From: Robert Hancock <hancockr@shaw.ca>
To: Greg.Chandler@wellsfargo.com
Cc: linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem
Date: Sun, 18 Mar 2007 23:20:09 -0600 [thread overview]
Message-ID: <45FE1D89.6020303@shaw.ca> (raw)
In-Reply-To: <E8C008223DD5F64485DFBDF6D4B7F71D0289EDBF@msgswbmnmsp25.wellsfargo.com>
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.
And what lspci reports is merely that the device supports 66MHz bus
speed. That doesn't mean it doesn't support higher speeds and that
doesn't mean that's what it's running at.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-03-19 5:20 UTC|newest]
Thread overview: 11+ 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 [this message]
2007-03-19 5:31 ` Willy Tarreau
2007-03-19 5:59 ` [E1000-devel] " Robin Humble
2007-03-19 6:56 ` Willy Tarreau
2007-03-18 18:51 Greg.Chandler
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=45FE1D89.6020303@shaw.ca \
--to=hancockr@shaw.ca \
--cc=Greg.Chandler@wellsfargo.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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