From: Jason Lunz <lunz@reflexsecurity.com>
To: "Filip Sneppe (Yucom)" <filip.sneppe@yucom.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to improve the throughput of linux network
Date: Tue, 16 Jul 2002 15:10:17 -0400 [thread overview]
Message-ID: <20020716191017.GA26500@reflexsecurity.com> (raw)
In-Reply-To: <1026838787.401.15.camel@xbox>
On Tue, Jul 16, 2002 at 6:59PM +0200, Filip Sneppe (Yucom) wrote:
> Hey, that's funny. I downloaded NAPI patches from:
> ftp://robur.slu.se/pub/Linux/net-development/NAPI/
Yes, that's where the NAPI stuff originates. The core patch from that
site is what made it into 2.5, and I backported it to 2.4 from there.
There are no substantial differences between the three.
> How different are those patches from yours ? Did you just make
> sure they all applied cleanly ?
While the core is mostly a matter of changing patch offsets, the driver
patches are still a moving target. There are two different flavors of
the e1000 NAPI patch, for example. The most recent tulip patch from the
above FTP site is missing tulip_misc.c, so it must be replaced with a
version from another patch. That file really is only code to report
stats in /proc, though. There's yet another napified tulip driver that
jamal posted a link to; I have yet to investigate that one.
But to answer your question, yes. I just found the most recent versions
of various napi efforts and made them apply to a recent 2.4 kernel so
people can easily try out the new net core.
Jason
next prev parent reply other threads:[~2002-07-16 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 1:13 how to improve the throughput of linux network zhengchuanbo
2002-07-16 14:26 ` Jason Lunz
[not found] ` <1026838787.401.15.camel@xbox>
2002-07-16 19:10 ` Jason Lunz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 2:44 RE:Re: " Hell.Surfers
2002-07-16 2:57 ` Thunder from the hill
2002-07-18 15:35 ` Eric W. Biederman
2002-07-17 14:13 zhengchuanbo
2002-07-17 16:29 ` Jason Lunz
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=20020716191017.GA26500@reflexsecurity.com \
--to=lunz@reflexsecurity.com \
--cc=filip.sneppe@yucom.be \
--cc=linux-kernel@vger.kernel.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