From: Andrew Morton <akpm@digeo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: manfred@colorfullife.com,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: Info: NAPI performance at "low" loads
Date: Tue, 17 Sep 2002 14:45:08 -0700 [thread overview]
Message-ID: <3D87A264.8D5F3AD2@digeo.com> (raw)
In-Reply-To: 20020917.142635.114214508.davem@redhat.com
"David S. Miller" wrote:
>
> From: Andrew Morton <akpm@digeo.com>
> Date: Tue, 17 Sep 2002 14:32:09 -0700
>
> There is a similar background loadtester at
> http://www.zip.com.au/~akpm/linux/#zc .
>
> It's fairly fancy - I wrote it for measuring networking
> efficiency. It doesn't seem to have any PCisms....
>
> Thanks I'll check it out, but meanwhile I hacked up sparc
> specific assembler for manfred's code :-)
>
> (I measured similar regression using an ancient NAPIfied
> 3c59x a long time ago).
>
> Well, it is due to the same problems manfred saw initially,
> namely just a crappy or buggy NAPI driver implementation. :-)
It was due to additional inl()'s and outl()'s in the driver fastpath.
Testcase was netperf Tx and Rx. Just TCP over 100bT. AFAIK, this overhead
is intrinsic to NAPI. Not to say that its costs outweigh its benefits,
but it's just there.
If someone wants to point me at all the bits and pieces to get a
NAPIfied 3c59x working on 2.5.current I'll retest, and generate
some instruction-level oprofiles.
next prev parent reply other threads:[~2002-09-17 21:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 19:53 Info: NAPI performance at "low" loads Manfred Spraul
2002-09-17 20:59 ` David S. Miller
2002-09-17 21:32 ` Andrew Morton
2002-09-17 21:26 ` David S. Miller
2002-09-17 21:45 ` Andrew Morton [this message]
2002-09-17 21:39 ` David S. Miller
2002-09-17 21:54 ` Jeff Garzik
2002-09-17 21:49 ` David S. Miller
2002-09-18 2:11 ` Jeff Garzik
2002-09-18 2:06 ` David S. Miller
2002-09-18 2:36 ` Jeff Garzik
2002-09-17 21:58 ` Andrew Morton
2002-09-18 0:57 ` jamal
2002-09-18 1:00 ` David S. Miller
2002-09-18 2:16 ` Andrew Morton
2002-09-18 17:27 ` Eric W. Biederman
2002-09-18 17:50 ` Alan Cox
2002-09-19 14:58 ` Eric W. Biederman
2002-09-18 20:23 ` David S. Miller
2002-09-18 20:43 ` Alan Cox
2002-09-18 20:46 ` David S. Miller
2002-09-18 21:15 ` Alan Cox
2002-09-18 21:22 ` David S. Miller
2002-09-19 15:03 ` Eric W. Biederman
2002-09-19 15:53 ` Alan Cox
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=3D87A264.8D5F3AD2@digeo.com \
--to=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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).