From: Willy Tarreau <w@1wt.eu>
To: Robin Humble <rjh+e1000@cita.utoronto.ca>
Cc: Robert Hancock <hancockr@shaw.ca>,
e1000-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Greg.Chandler@wellsfargo.com
Subject: Re: [E1000-devel] 1000xf bus problem
Date: Mon, 19 Mar 2007 07:56:41 +0100 [thread overview]
Message-ID: <20070319065641.GA7550@1wt.eu> (raw)
In-Reply-To: <20070319055932.GA17345@lemming.cita.utoronto.ca>
On Mon, Mar 19, 2007 at 01:59:32AM -0400, Robin Humble wrote:
> On Mon, Mar 19, 2007 at 06:31:51AM +0100, Willy Tarreau wrote:
> >On Sun, Mar 18, 2007 at 11:20:09PM -0600, Robert Hancock wrote:
> >> Greg.Chandler@wellsfargo.com wrote:
> >> >lspci -v shows the message below, and I am moving files between systems,
> >> >{from RAMdisk to RAMdisk} on idle machines.
> >> >The transfer rate is concurrent with just under the max throughput
> >> >capable on a 64-bit/66Mhz PCI socket.
> >>
> >> I think you miscalculate, that bus can transfer 532 MB/sec, Gigabit
> >> Ethernet tops out at 125 MB/sec at absolute maximum and it's difficult
> >> to achieve that in practice.
> >
> >On TCP payload, you should achieve 118.66 * 10^6 bytes/s ~= 113 MB/s.
>
> times 2 for full duplex.
perfectly, I was talking about something easy to measure (ftp...)
> so a 32bit/33MHz bus = 132MB/s isn't enough for fdx, but anything more
> (64bit or 66MHz or both) should be fine.
Not even, in fact, you have to subtract the PCI overhead. It is very hard to
go beyond 800 Mbps half duplex on PCI/33/32bits, so if you have either 64bits
or 66 MHz, you won't go past 1.6 Gbps FD, or a little less than 200 MB/s.
66*64 is really required to simultaneously achieve 1 Gbps in both directions.
Regards,
Willy
prev parent reply other threads:[~2007-03-19 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
2007-03-18 19:41 ` 1000xf bus problem Robert Hancock
2007-03-18 20:51 ` Kok, Auke
2007-03-19 3:03 ` Greg.Chandler
2007-03-19 3:39 ` Kok, Auke
2007-03-19 3:48 ` Greg.Chandler
2007-03-19 2:53 ` Greg.Chandler
2007-03-19 5:20 ` Robert Hancock
2007-03-19 5:31 ` Willy Tarreau
2007-03-19 5:59 ` [E1000-devel] " Robin Humble
2007-03-19 6:56 ` Willy Tarreau [this message]
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=20070319065641.GA7550@1wt.eu \
--to=w@1wt.eu \
--cc=Greg.Chandler@wellsfargo.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rjh+e1000@cita.utoronto.ca \
/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