From: Jeff Garzik <jgarzik@pobox.com>
To: Boris Protopopov <borisp@mc.com>
Cc: jamal <hadi@cyberus.ca>, Cheng Jin <chengjin@cs.caltech.edu>,
netdev@oss.sgi.com
Subject: Re: Linux SMP on 2.4.18-3
Date: Tue, 29 Oct 2002 20:54:36 -0500 [thread overview]
Message-ID: <3DBF3BDC.8030902@pobox.com> (raw)
In-Reply-To: 3DBF3881.6070208@mc.com
Boris Protopopov wrote:
> Jamal, could you give some pointers as to how "NAPIfy" a
> 2.4.18-3/e1000-4.3.15 setup ? Boris.
In general, read Documentation/networking/NAPI_HOWTO.txt.
For e1000 specifically, copy drivers/net/e1000/*.[ch] to 2.4.x.
Jeff
prev parent reply other threads:[~2002-10-30 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 8:27 Linux SMP on 2.4.18-3 Cheng Jin
2002-10-28 12:47 ` jamal
2002-10-28 18:26 ` Cheng Jin
2002-10-30 19:03 ` Robert Olsson
2002-10-31 7:55 ` Network Device-Driver/Layer Implementation: Help required Harish Kulkarni
2002-10-31 16:35 ` James R. Leu
2002-11-04 13:10 ` Linux SMP on 2.4.18-3 jamal
2002-10-30 1:40 ` Boris Protopopov
2002-10-30 1:54 ` Jeff Garzik [this message]
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=3DBF3BDC.8030902@pobox.com \
--to=jgarzik@pobox.com \
--cc=borisp@mc.com \
--cc=chengjin@cs.caltech.edu \
--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).