From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: NAPI: dev.c change to net_rx_action algorithm.
Date: Fri, 08 Nov 2002 20:55:17 -0800 [thread overview]
Message-ID: <3DCC9535.3050506@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0211082326220.16986-100000@shell.cyberus.ca
jamal wrote:
>
> The only thing i can think of is that if it was legal to flog people
> youd be on my list. And i would hope you dont enjoy it.
> Why do you like to put band-aids to things?
> Find the real cause of why you may be having problems then cure it;
> putting arbitrary hacks just because you can is rather against
> the basic principles of engineering.
>
> cheers,
> jamal
I'm looking for the real cause. The current code does not work
as I want it to. So, I'm changing things. I would love to try
out any patch you might feel like contributing.
From what I can tell, the old code punishes interfaces who are
running slower at any given time. My change, I believe, will
allow slower interfaces to gather a bit more quota so that when
they are hit with a burst of traffic, they can spend a little
extra time to clear their buffers.
I would also welcome any argument as to why my code is worse
than the existing code. And theoretical papers be damned,
I see better results with the change below. Why is that?
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-11-09 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 4:23 NAPI: dev.c change to net_rx_action algorithm Ben Greear
2002-11-09 4:32 ` jamal
2002-11-09 4:55 ` Ben Greear [this message]
2002-11-09 4:58 ` jamal
2002-11-09 5:30 ` Ben Greear
2002-11-09 14:41 ` 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=3DCC9535.3050506@candelatech.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.