From: urgrue <urgrue@tumsan.fi>
To: Neil Horman <nhorman@redhat.com>
Cc: linux-admin@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Linux based router for Gigabit traffic
Date: Mon, 23 Aug 2004 14:36:41 +0300 [thread overview]
Message-ID: <20040823113641.GC16414@fede2.tumsan.fi> (raw)
In-Reply-To: <4129D23C.4040604@redhat.com>; from nhorman@redhat.com on Mon, Aug 23, 2004 at 14:17:16 +0300
On 2004.08.23 14:17, Neil Horman wrote:
> Really? What are PCI bus transfer rates up to these days? I havent
> looked into it in quite a while.
> N3il
Your average 33mhz PCI bus has a paltry maximum bandwidth of 1 gbps.
Full-duplex gigabit routing on more than one interface pretty much
requires PCI Express. Here's a little table:
PCI32 33MHz = 133MB/s PCI32 66MHz = 266MB/s PCI64 33MHz = 266MB/s
PCI64 66MHz = 533MB/s
PCI-X 133MHz = 1066MB/s
Also gigabit routing on your average unmodified linux distribution
requires a VERY hefty CPU to keep up, even just with two or three
gigabit interfaces.
next prev parent reply other threads:[~2004-08-23 11:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 12:32 Linux based router for Gigabit traffic Anantha Kiran
2004-08-22 12:49 ` Neil Horman
2004-08-23 5:56 ` David S. Miller
2004-08-23 7:11 ` Mikael Abrahamsson
2004-08-23 13:10 ` Adam Lang
2004-08-23 7:58 ` urgrue
2004-08-23 11:17 ` Neil Horman
2004-08-23 11:36 ` urgrue [this message]
2004-08-25 7:48 ` Stephen Samuel
2004-08-23 15:31 ` Stephen J. Smoogen
2004-08-24 17:08 ` DNS "named" question Tony Gogoi
2004-08-24 17:21 ` DNS 'named' question Scott Taylor
2004-08-24 17:33 ` DNS "named" question Bradley Hook
2004-08-22 15:07 ` Linux based router for Gigabit traffic Matti Aarnio
2004-08-27 18:01 ` neolozer
[not found] <Pine.LNX.4.44.0408220858160.1897-100000@bawx.pilosoft.com>
[not found] ` <4128CA84.7000304@redhat.com>
2004-08-22 18:14 ` Anantha Kiran
2004-08-22 18:25 ` Anantha Kiran
2004-08-23 15:39 ` Stephen J. Smoogen
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=20040823113641.GC16414@fede2.tumsan.fi \
--to=urgrue@tumsan.fi \
--cc=linux-admin@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=nhorman@redhat.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).