From: P@draigBrady.com
To: Harald Welte <laforge@netfilter.org>
Cc: Linux NICS <linux.nics@intel.com>, netdev@oss.sgi.com
Subject: Re: TX performance of Intel 82546
Date: Wed, 15 Sep 2004 10:18:43 +0100 [thread overview]
Message-ID: <414808F3.70104@draigBrady.com> (raw)
In-Reply-To: <20040915081439.GA27038@sunbeam.de.gnumonks.org>
Harald Welte wrote:
> Hi!
>
> I'm currently trying to help Robert Olsson improving the performance of
> the Linux in-kernel packet generator (pktgen.c). At the moment, we seem
> to be unable to get more than 760kpps from a single port of a 82546,
> (or any other PCI-X MAC supported by e1000) - that's a bit more than 51%
> wirespeed at 64byte packet sizes.
In my experience anything around 750Kpps is a PCI limitation,
specifically PCI bus arbitration latency. Note the clock speed of
the control signal used for bus arbitration has not increased
in proportion to the PCI data clock speed.
The application note #453 referenced below is very imformative:
http://www.intel.com/design/network/products/lan/docs/82546_docs.htm
I was able to confirm the above by passing 4x730Kpps
through a PCI-X system with 4 ethernet controllers,
but never more than 760Kpps through one particular controller.
Note also you may be able to tune for transmission
using setpci (google for setpci & MMRBC), or hacking with TSO?
Pádraig.
next prev parent reply other threads:[~2004-09-15 9:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 8:14 TX performance of Intel 82546 Harald Welte
2004-09-15 9:18 ` P [this message]
2004-09-15 12:18 ` jamal
2004-09-15 14:02 ` Harald Welte
2004-09-15 14:46 ` jamal
2004-09-15 14:55 ` Andi Kleen
2004-09-15 12:36 ` Robert Olsson
2004-09-15 13:49 ` jamal
2004-09-15 15:33 ` Robert Olsson
2004-09-15 13:59 ` P
2004-09-15 15:41 ` Robert Olsson
2004-09-15 18:15 ` Harald Welte
2004-09-15 18:15 ` David S. Miller
2004-09-15 17:55 ` Harald Welte
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=414808F3.70104@draigBrady.com \
--to=p@draigbrady.com \
--cc=laforge@netfilter.org \
--cc=linux.nics@intel.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).