From: Dave Hansen <haveblue@us.ibm.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: netdev@oss.sgi.com, Scott Feldman <scott.feldman@intel.com>
Subject: Re: impressive throughput on 2.5.73
Date: 02 Jul 2003 20:20:52 -0700 [thread overview]
Message-ID: <1057202451.2916.36.camel@nighthawk> (raw)
In-Reply-To: <3F039BE1.2080008@us.ibm.com>
On Wed, 2003-07-02 at 19:58, Nivedita Singhvi wrote:
> Nice numbers :). In addition to NAPI, would be nice to
> stick in more adapters. Any idea why __wake_up should be
> so expensive on the client side?
NAPI seems to degrade throughput down to ~80MB/sec, but the interrupt
rate doesn't change. I'm going to put some debugging in and makes sure
that it's kicking in properly.
--
Dave Hansen
haveblue@us.ibm.com
prev parent reply other threads:[~2003-07-03 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 0:56 impressive throughput on 2.5.73 Dave Hansen
2003-07-03 2:58 ` Nivedita Singhvi
2003-07-03 3:20 ` Dave Hansen [this message]
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=1057202451.2916.36.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=scott.feldman@intel.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).