public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Ben Greear <greearb@candelatech.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>
Subject: NAPI (was Re: Linux 2.4.20-pre1)
Date: Tue, 06 Aug 2002 13:12:04 -0400	[thread overview]
Message-ID: <3D500364.5010607@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208060832090.6811-100000@freak.distro.conectiva

Marcelo Tosatti wrote:
> I want arguments from Davem to include NAPI. Changing the drivers is a
> reason for me to _not_ want it in.
> 
> But lets see if Davem can convince me ;)



8139too needs it for flood protection.  I also have a patch for sundance 
which fixes the issue with the quad port and implements RX polling for 
flood protection.

Basically, NAPI --should not-- affect any system that is not using a 
NAPI driver.  Think of NAPI as a net driver libary -- if your driver 
doesn't use it, you don't know it's there at all.  And currently tg3 is 
the only 2.4 driver using NAPI.

NAPI saves people manually implementing polling in each driver, for 
flood and DoS protection that is needed in 2.4.  The flood ceiling is 
much lower without NAPI, due to having the CPU overhead of interrupt 
handlers.  NAPI also eliminates the need for lots of code to support all 
sorts of NIC hardware interrupt mitigation variants.

	Jeff




  parent reply	other threads:[~2002-08-06 17:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 22:40 Linux 2.4.20-pre1 Marcelo Tosatti
2002-08-06  0:20 ` Ben Greear
2002-08-06 11:32   ` Marcelo Tosatti
2002-08-06 12:26     ` David S. Miller
2002-08-06 16:45     ` Ben Greear
2002-08-06 17:12     ` Jeff Garzik [this message]
2002-08-07 14:09       ` NAPI (was Re: Linux 2.4.20-pre1) Marcus Sundberg
2002-08-06 14:58 ` Linux 2.4.20-pre1 Jason Lunz
2002-08-06 15:03   ` CaT
2002-08-06 21:05 ` Adrian Bunk
2002-08-07 11:09   ` David S. Miller
2002-08-07  0:21 ` J.A. Magallon
2002-08-07  1:08 ` J.A. Magallon
2002-08-07  1:56 ` Bryan Whitehead
2002-08-07  3:35   ` Tim Hockin
2002-08-11  8:57 ` Erik Andersen
2002-08-11  9:16   ` Christoph Hellwig
2002-08-11  9:40     ` Erik Andersen
2002-08-11  9:46     ` Erik Andersen
2002-08-11 19:46   ` Alan Cox
2002-08-11 18:49     ` Erik Andersen
2002-08-12 19:29     ` Paul P Komkoff Jr
2002-08-11 10:56 ` Erik Andersen
2002-08-11 21:22 ` [PATCH] radeonfb update vs 2.4.20-pre1 Erik Andersen
2002-08-12 10:18   ` Ani Joshi
2002-08-12 10:26     ` Erik Andersen
2002-08-17 19:51 ` Linux 2.4.20-pre1 Adrian Bunk

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=3D500364.5010607@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=davem@redhat.com \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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