From: Jason Lunz <lunz@falooley.org>
To: jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com, Robert.Olsson@data.slu.se,
greearb@candelatech.com, garzik@mandrakesoft.com
Subject: Re: [ANNOUNCE] NAPI patches for 2.4.19-rc1
Date: Thu, 11 Jul 2002 09:26:04 -0400 [thread overview]
Message-ID: <20020711132604.GC12354@orr.falooley.org> (raw)
In-Reply-To: <Pine.GSO.4.30.0207101917480.22734-100000@shell.cyberus.ca>
On Wed, Jul 10, 2002 at 7:34PM -0400, jamal wrote:
> For some reason i thought there was already patches for 2.4.18 and above.
> Robert, seems like you dont have them;
> Two patches:
> 2.4.18: http://www.cyberus.ca/~hadi/patches/napi-patch-2418.gz
> 2.4.19-pre10: http://www.cyberus.ca/~hadi/patches/napi-2419-pre10.gz
ah, thanks! The napi README links to the usenix paper on your site, but
doesn't mention the patches directory.
> Also a more recently tested tulip driver at:
> http://www.cyberus.ca/~hadi/patches/tulip-napi.tgz
great, I'll check it out too.
> tested with Znyx 4 port ethernet cards; For the best perfomance (at
> least on the Znyx Nics) turn on MMIO (selected from kernel config).
Do you know if this would also apply to the DLink 4-port tulip cards
(DFE-570TX)? They're based on intel 21143's.
Jason
next prev parent reply other threads:[~2002-07-11 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 22:32 [ANNOUNCE] NAPI patches for 2.4.19-rc1 Jason Lunz
2002-07-10 22:56 ` Ben Greear
2002-07-11 13:20 ` Jason Lunz
2002-07-10 23:34 ` jamal
2002-07-11 0:41 ` Donald Becker
2002-07-11 14:57 ` Jeff Garzik
2002-07-11 16:50 ` Donald Becker
2002-07-11 17:17 ` Ben Greear
2002-07-11 18:31 ` Jeff Garzik
2002-07-11 22:31 ` Ben Greear
2002-07-12 15:11 ` Jason Lunz
2002-07-11 18:53 ` Donald Becker
2002-07-11 19:34 ` Jeff Garzik
2002-07-11 13:26 ` Jason Lunz [this message]
2002-07-11 13:39 ` Jeff Garzik
2002-07-11 13:44 ` Jason Lunz
2002-07-11 14:33 ` Donald Becker
2002-07-11 14:37 ` Jeff Garzik
2002-07-11 16:00 ` Robert Olsson
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=20020711132604.GC12354@orr.falooley.org \
--to=lunz@falooley.org \
--cc=Robert.Olsson@data.slu.se \
--cc=garzik@mandrakesoft.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).