From: Nivedita Singhvi <niv@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: netdev@oss.sgi.com, Scott Feldman <scott.feldman@intel.com>
Subject: Re: impressive throughput on 2.5.73
Date: Wed, 02 Jul 2003 19:58:41 -0700 [thread overview]
Message-ID: <3F039BE1.2080008@us.ibm.com> (raw)
In-Reply-To: <1057193766.31286.843.camel@nighthawk>
Dave Hansen wrote:
> 176 requests/sec - 110.0 MB/second - 0.6 MB/request
>
> Server CPU breakdown.
> 2% system
> 7% user
> 91% idle
>
> client profile:
> 33363 total 0.0196
> 9575 poll_idle 132.9861
> 5099 __copy_user_intel 32.6859
> 3307 schedule 2.1418
> 1753 __wake_up 39.8409
> 667 tcp_v4_rcv 0.3382
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?
thanks,
Nivedita
next prev parent reply other threads:[~2003-07-03 2:58 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 [this message]
2003-07-03 3:20 ` Dave Hansen
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=3F039BE1.2080008@us.ibm.com \
--to=niv@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=netdev@oss.sgi.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).