From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Intel Pro/1000 PT support?
Date: Mon, 12 Nov 2007 17:58:41 -0800 [thread overview]
Message-ID: <179078CB-5E08-4F42-8020-0BEBA81CDB75@orthanc.ca> (raw)
In-Reply-To: <225e6f4e59d66eacba8ad8459c59f9f9@quanstro.net>
On 2007-Nov-12, at 17:34 , erik quanstrom wrote:
> by the way, we've found the pro/1000 pt dual to be more cost-
> effective.
> if you have too many ports to use 2 dual cards, it would probablly be
> more effective to use myricom cards with 10gbaseCX4 ports
Thanks for the info Erik. I'll do a cost comparison between the 2x2
vs. 1x4 config. Traffic volume isn't a big concern — this is for a
machine that will be a (mostly) passive network monitor for several
LAN segments at a remote site.
--lyndon
next prev parent reply other threads:[~2007-11-13 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 1:20 Lyndon Nerenberg
2007-11-13 1:25 ` Pietro Gagliardi
2007-11-13 1:33 ` Lyndon Nerenberg
2007-11-13 1:38 ` erik quanstrom
2007-11-13 1:34 ` erik quanstrom
2007-11-13 1:58 ` Lyndon Nerenberg [this message]
2007-11-13 2:03 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179078CB-5E08-4F42-8020-0BEBA81CDB75@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).