From: jamal <hadi@cyberus.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com, "" <linux-net@vger.kernel.org>
Subject: Re: NAPI interrupt data
Date: Sat, 15 Feb 2003 09:34:02 -0500 (EST) [thread overview]
Message-ID: <20030215092908.E16812@shell.cyberus.ca> (raw)
In-Reply-To: <3E4DE95C.2050804@pobox.com>
On Sat, 15 Feb 2003, Jeff Garzik wrote:
> bash-2.05b$ ./x.pl data.crumb
> 135 samples, 21578 avg
> bash-2.05b$ ./x.pl data.hum
> 130 samples, 11213 avg
>
Probably the first 5-10 samples as well as the last 5-10 amples to get
more accuracy.
This data looks fine, no? definetly the scsi device is skewing things
(you are writting data to disk for example).
- The 500Kpps from ttcp doesnt sound right; tcp will slow you down.
perhaps use ttcp to send udp packets to get a more interesting view.
cheers,
jamal
next prev parent reply other threads:[~2003-02-15 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-15 7:16 NAPI interrupt data Jeff Garzik
2003-02-15 7:24 ` Jeff Garzik
2003-02-15 14:34 ` jamal [this message]
2003-02-15 18:55 ` Jeff Garzik
2003-02-15 22:14 ` jamal
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=20030215092908.E16812@shell.cyberus.ca \
--to=hadi@cyberus.ca \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.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).