From: Stephen Hemminger <shemminger@vyatta.com>
To: rostedt@goodmis.org
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Michael Buesch <mb@bu3sch.de>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Matt Smith <Matt.Smith@atheros.com>,
Kevin Hayes <kevin@atheros.com>,
Bob Copeland <me@bobcopeland.com>, Jouni Malinen <j@w1.fi>,
Ivan Seskar <Seskar@winlab.rutgers.edu>,
ic.felix@gmail.com
Subject: Re: Stop using tasklets for bottom halves
Date: Tue, 8 Sep 2009 10:01:44 -0700 [thread overview]
Message-ID: <20090908100144.6e06872b@nehalam> (raw)
In-Reply-To: <1252428023.15626.30.camel@gandalf.stny.rr.com>
On Tue, 08 Sep 2009 12:40:23 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 2009-09-08 at 09:11 -0700, Stephen Hemminger wrote:
>
> > > > Process context is too slow.
> > >
> > > Well, I'm hoping to prove the opposite. I'm working on some stuff that I
> > > plan to present at Linux Plumbers. I've been too distracted by other
> > > things, but hopefully I'll have some good numbers to present by then.
> > >
> >
> >
> > That's great, does it keep the good properties of NAPI (irq disabling
> > and throttling?)
>
> Not exactly sure what you mean by throttling, but I'm assuming it will.
>
> As for irqs disabling, I'm trying to avoid doing that. Note, the device
> will have its interrupts disabled, but not all other devices will.
>
> -- Steve
>
>
The way NAPI works is that in irq routine, the device disables interrupts
then schedules processing packets, when processing is done irq's are re-enabled.
This means that if machine is being flooded, irq's stay off, and the packets
get discarded (because device hardware ring is full), rather than in software
(because software receive queue is full).
--
next prev parent reply other threads:[~2009-09-08 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 22:58 Stop using tasklets for bottom halves Luis R. Rodriguez
2009-09-08 0:14 ` Stephen Hemminger
2009-09-08 2:17 ` Steven Rostedt
[not found] ` <1252376254.21261.2052.camel-f9ZlEuEWxVcI6MkJdU+c8EEOCMrvLtNR@public.gmane.org>
2009-09-08 4:16 ` Luis R. Rodriguez
[not found] ` <43e72e890909072116v33ecafc4ma7f5a68825f14e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-08 13:18 ` Steven Rostedt
2009-09-08 4:50 ` Michael Buesch
2009-09-08 5:08 ` Michael Buesch
2009-09-08 7:10 ` Ingo Molnar
2009-09-08 16:11 ` Stephen Hemminger
2009-09-08 16:40 ` Steven Rostedt
2009-09-08 17:01 ` Stephen Hemminger [this message]
2009-09-08 17:27 ` Steven Rostedt
2009-09-08 16:12 ` Stephen Hemminger
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=20090908100144.6e06872b@nehalam \
--to=shemminger@vyatta.com \
--cc=Matt.Smith@atheros.com \
--cc=Seskar@winlab.rutgers.edu \
--cc=ic.felix@gmail.com \
--cc=j@w1.fi \
--cc=kevin@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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).