From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Netdev <netdev@oss.sgi.com>
Subject: crappy/good gigabit chipsets?
Date: Sat, 27 Nov 2004 07:17:57 +0100 [thread overview]
Message-ID: <41A81C15.5080905@gmx.net> (raw)
Hi,
I'm trying to build a gigabit ethernet bridge with Linux 2.6 and
commodity hardware. The bridge should be able to filter traffic
(probably with ebtables), which will mostly be operations like
"drop traffic from this host", "drop traffic to this port", to
stop infected windows machines generating traffic until they are
reformatted with Linux.
The traffic source is a 100 MBit switched network with 2500 PCs
(1 GBit Uplink) and the usual frame sizes on a switched 100 MBit
network and the sink is a machine doing masquerading of the
internal machines to the outside world.
IIRC, TSO, hardware checksumming etc. are abolutely unneeded for
this type of operation, but a fast transfer of the packets to/
from memory is essential. Maybe I'm crazy to assume a current
machine with classic 32 bit PCI bus can handle such a load, but
since Linux performs stellar with a bunch of 100 MBit cards at
the same time, I see at least some hope.
Which gigabit chipsets do classic data transfer fast enough to
get a recommendation from the experts?
Which gigabit drivers are stable und well-written enough to
sustain fully loaded interfaces without breaking down?
Which chipsets should be avoided?
Thank you very much for your time.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next reply other threads:[~2004-11-27 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 6:17 Carl-Daniel Hailfinger [this message]
2004-11-27 11:10 ` crappy/good gigabit chipsets? Lennert Buytenhek
2004-11-27 13:47 ` Francois Romieu
2004-11-27 20:14 ` Lennert Buytenhek
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=41A81C15.5080905@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=netdev@oss.sgi.com \
/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).