From: "John William" <jw2357@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Network Performance Testing Summary
Date: Wed, 06 Jun 2001 02:52:03 [thread overview]
Message-ID: <F120XA946xFRFtReq5G0000dddd@hotmail.com> (raw)
This is a follow up message to the original "Abysmal Receive Performance"
message. Thanks to everyone who e-mailed me with suggestions.
Well, after poking around, I eventually narrowed the problem down to the
fact that the system BIOS did not enable PCI->RAM write posting. After I
enabled that with the bridge optimization setting in 2.2.19, network RECV
performance went from ~5Mbps to 41Mbps.
The curse of the HP Vectra XU 5/90 strikes again!
What is interesting is that I tried the NetGear FA310, FA311, 3COM 3cSOHO
and 3C905C-TX cards and both the receive and transmit speeds (measured with
both iperf and netperf) were so close to each other as to be a non-issue.
Several people e-mailed me to let me know that "card 'X' performance is
terrible, I can only get good performance with card 'Y'". So, I just thought
I should send this message out to set things a bit straight.
I know this machine isn't exactly cutting-edge, but I have to admit I was a
little surprised to see all four of the cards I tested clustered so close
together (so close, that you could call it 41.8Mpbs RECV and 52.2Mbps XMIT
for all cards).
FWIW, it is somewhat interesting that 2.4.3 performance is so horrible with
PCI->RAM posting disabled, whereas 2.2.19 doesn't take nearly the same hit.
Using the 1.1.7 Tulip driver from Sourceforge didn't change this at all.
With write posting enabled, things 2.4.3 ended up performing better than
2.2.19.
So, thanks to everyone who helped me out. Looks like I now need to start a
FAQ just for Vectra XU 5/90 owners so they can get their machines to work...
- John
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
next reply other threads:[~2001-06-06 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 2:52 John William [this message]
2001-06-06 4:30 ` David Rees
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=F120XA946xFRFtReq5G0000dddd@hotmail.com \
--to=jw2357@hotmail.com \
--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
all inboxes | Powered by JetHome®