From: Jason Lunz <lunz@falooley.org>
To: netdev@oss.sgi.com
Subject: Re: [Fwd: [E1000] NAPI re-insertion w/ changes]
Date: Thu, 27 Mar 2003 17:10:03 +0000 (UTC) [thread overview]
Message-ID: <slrnb86c3g.7vo.lunz@stoli.localnet> (raw)
In-Reply-To: 16003.11449.497905.815776@robur.slu.se
Robert.Olsson@data.slu.se said:
> 10 Million pkts injected at high speed into eth2 and forwarded to eth3. Rx and
> Tx buffers are 256 and HW_FLOW is disabled and RxIntDelay=1. Which is same
> parameters as we use for production systems. As seen link now flaps.
> Eventually can hw_flowcontrol and interrupt delays help this... but thats not
> an option at least not for us.
>
>
> Twist: New Old
> ====================================
> Input rate: 680 (due to link drop) 820 kpps
> T-put: 309 385 kpps
> RX irq's: 78963 434
I've seen pretty much the same thing. I plotted throughput vs. offered
load for e1000 4.4.12-k1, 4.4.19-k3, and 5.0.43-k1 (all backported to
2.4.20). A summary with graphs is at:
http://gtf.org/lunz/linux/net/perf/
5.0.43 seems to be a significant regression, both in terms of throughput
and CPU load.
--
Jason Lunz Reflex Security
lunz@reflexsecurity.com http://www.reflexsecurity.com/
next prev parent reply other threads:[~2003-03-27 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 16:54 [Fwd: [E1000] NAPI re-insertion w/ changes] Robert Olsson
2003-03-27 17:10 ` Jason Lunz [this message]
2003-03-28 8:27 ` Robert Olsson
2003-03-28 17:32 ` Jason Lunz
2003-03-28 18:43 ` Robert Olsson
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 0:13 Feldman, Scott
2003-04-02 4:19 ` Jason Lunz
2003-04-01 21:22 Feldman, Scott
2003-04-01 19:13 Feldman, Scott
2003-04-01 19:23 ` Jason Lunz
2003-04-01 22:40 ` Jason Lunz
2003-04-01 19:44 ` Robert Olsson
2003-04-01 17:47 Feldman, Scott
2003-04-01 18:57 ` Robert Olsson
2003-04-01 21:16 ` Jeff Garzik
2003-03-22 18:47 Feldman, Scott
2003-03-22 20:28 ` Robert Olsson
2003-03-31 17:14 ` Robert Olsson
2003-03-21 14:46 Jeff Garzik
2003-03-22 15:34 ` Robert Olsson
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=slrnb86c3g.7vo.lunz@stoli.localnet \
--to=lunz@falooley.org \
--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).