From: Jeff Garzik <jgarzik@pobox.com>
To: Octave <oles@ovh.net>
Cc: Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: NAPI 8139too.c for 2.4.23
Date: Mon, 1 Dec 2003 15:55:33 -0500 [thread overview]
Message-ID: <20031201205533.GA15846@gtf.org> (raw)
In-Reply-To: <20031201205038.GK10711@ovh.net>
On Mon, Dec 01, 2003 at 09:50:38PM +0100, Octave wrote:
> Stephen,
> I get your patch from http://lwn.net/Articles/54815/ for 2.6.X and
> I rewrote it for 2.4.23. Tested with 2.4.23 on high load servers. I
> have no more "Too much work at interrupt".
>
> I dropped it on ftp://ftp.ovh.net/made-in-ovh/8139too.c-2.4-0.9.27
>
> Hope it helps.
> Octave
Very cool! Thanks for testing.
Is there any chance you could do some benchmark runs with ttcp or
somesuch?
Jeff
next prev parent reply other threads:[~2003-12-01 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 20:50 NAPI 8139too.c for 2.4.23 Octave
2003-12-01 20:55 ` Jeff Garzik [this message]
2003-12-01 23:00 ` Octave
2003-12-01 23:39 ` Ben Greear
2003-12-02 3:47 ` Jeff Garzik
2003-12-01 21:13 ` Marcello
2003-12-01 22:32 ` Marcello
2003-12-01 22:54 ` Marcello
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=20031201205533.GA15846@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=oles@ovh.net \
--cc=shemminger@osdl.org \
/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).