From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Ben Greear <greearb@candelatech.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: 2.6.7 tulip performance (with NAPI)
Date: Fri, 8 Oct 2004 00:13:44 +0200 [thread overview]
Message-ID: <16741.49048.717774.307462@robur.slu.se> (raw)
In-Reply-To: <4165B981.8060703@candelatech.com>
Ben Greear writes:
> You must have several PCI-X busses on that system? From what I can tell,
> my dual-xeon system (2.8Ghz, X5DPA-GG motherboard) just can't handle the
> PCI bandwidth. I still have processing power it appears, and I see lots
> of hard-start-xmit errors out of the pro/1000 NICs, so I assume I am
> able to drive them as hard as they can go... It may be that receiving
> the pkts, as I am doing, also decreases transmit in more than a linear fashion.
Yes the board has 4 different PCI-bus from what I remember it's was a
Supermicro X5DL8-GG. Yes you need bus bandwith from what I've seen even
133 MHz PCI-X is limiting the small packet performance at GIGE speeds.
> > I'm interested if anyone has done any pktgen performance tests with
> > w. S2IO or other 10G card we need to upgrade the lab equipment.
> > Both 64 byte pkts and MTU sized pkts is interesting. Anyone?
>
> Not I, but would be interested as well!
Andi got one... ;-)
--ro
next prev parent reply other threads:[~2004-10-07 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 23:42 2.6.7 tulip performance (with NAPI) Ben Greear
2004-10-06 19:21 ` Robert Olsson
2004-10-06 21:37 ` Ben Greear
2004-10-07 0:56 ` Ben Greear
2004-10-07 1:08 ` David S. Miller
2004-10-07 18:09 ` Ben Greear
2004-10-11 4:07 ` David S. Miller
2004-10-07 21:11 ` Robert Olsson
2004-10-07 21:47 ` Ben Greear
2004-10-07 22:13 ` Robert Olsson [this message]
2004-10-07 23:44 ` Lennert Buytenhek
2004-10-08 9:25 ` P
2004-10-08 9:28 ` 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=16741.49048.717774.307462@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=greearb@candelatech.com \
--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).