From: Robert Olsson <Robert.Olsson@data.slu.se>
To: greear@candelatech.com
Cc: jamal <hadi@cyberus.ca>, Ben Greear <greearb@candelatech.com>,
Donald Becker <becker@scyld.com>,
"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: NAPI-ized tulip patch against 2.4.20-rc1
Date: Thu, 7 Nov 2002 22:26:04 +0100 [thread overview]
Message-ID: <15818.55916.259489.688198@robur.slu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0211071013150.31376-100000@grok.yi.org>
greear@candelatech.com writes:
> On Thu, 7 Nov 2002, jamal wrote:
> > Trash the machines harder. Try using smaller packets;
>
> They are already dropping packets, I thought I'd try to get a slower run
> to work cleanly before trying something faster. Precision is more
> important to me than absolute throughput at this point.
If you need excessive buffering this gives latency and jitter which is
considered bad for network protocols and worse for test equipment.
> Initial run with 256 sized rx-ring (and skb-recycle) shows better
> performance (than with 1024 rx-ring)
Packet size? Expect eventual effects when there is very high pressure on
the packet memory system.
Cheers.
--ro
next prev parent reply other threads:[~2002-11-07 21:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 6:36 NAPI-ized tulip patch against 2.4.20-rc1 Ben Greear
2002-11-06 6:42 ` Ben Greear
2002-11-06 17:34 ` Robert Olsson
2002-11-06 17:49 ` Ben Greear
2002-11-06 18:31 ` Donald Becker
2002-11-06 18:44 ` Ben Greear
2002-11-06 20:47 ` Donald Becker
2002-11-07 7:08 ` Ben Greear
2002-11-07 13:24 ` jamal
2002-11-07 18:16 ` greear
2002-11-07 21:26 ` Robert Olsson [this message]
2002-11-07 21:25 ` Ben Greear
2002-11-07 23:29 ` Ben Greear
2002-11-08 11:30 ` jamal
2002-11-08 17:40 ` Ben Greear
2002-11-07 12:57 ` jamal
2002-11-06 19:47 ` Robert Olsson
2002-11-06 21:30 ` Ben Greear
2002-11-07 12:48 ` 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=15818.55916.259489.688198@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=becker@scyld.com \
--cc=greear@candelatech.com \
--cc=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--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).