From: Lee Revell <rlrevell@joe-job.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: vda@port.imtp.ilyichevsk.odessa.ua,
Linux Network Development <netdev@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: tun.c patch to fix "smp_processor_id() in preemptible code"
Date: Tue, 19 Oct 2004 17:51:17 -0400 [thread overview]
Message-ID: <1098222676.23367.18.camel@krustophenia.net> (raw)
In-Reply-To: <E1CK1e6-0004F3-00@gondolin.me.apana.org.au>
On Tue, 2004-10-19 at 17:35, Herbert Xu wrote:
> Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > I looked at Robert Love's book and I am still unclear on the use of
> > do_softirq above. To reiterate the question: why does netif_rx_ni have
> > to manually flush any pending softirqs on the current proccessor after
> > doing the rx? Is this just a performance hack?
>
> Yes it allows the packet to be processed immediately.
Ok, here is the correct patch. If this is really just a matter of
performance, and not required for correctness, disabling preemption is
broken, right?
Lee
--- include/linux/netdevice.h~ 2004-10-15 20:19:33.000000000 -0400
+++ include/linux/netdevice.h 2004-10-19 17:47:03.000000000 -0400
@@ -697,8 +697,6 @@
static inline int netif_rx_ni(struct sk_buff *skb)
{
int err = netif_rx(skb);
- if (softirq_pending(smp_processor_id()))
- do_softirq();
return err;
}
next prev parent reply other threads:[~2004-10-19 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1097876587.4170.16.camel@marvin.home.parkautomat.net>
[not found] ` <1097879702.6737.7.camel@krustophenia.net>
[not found] ` <200410172314.38597.vda@port.imtp.ilyichevsk.odessa.ua>
2004-10-19 18:31 ` tun.c patch to fix "smp_processor_id() in preemptible code" Lee Revell
2004-10-19 21:35 ` Herbert Xu
2004-10-19 21:51 ` Lee Revell [this message]
2004-10-19 21:54 ` Herbert Xu
2004-10-19 22:10 ` Lee Revell
2004-10-19 22:33 ` David S. Miller
2004-10-19 22:42 ` Lee Revell
2004-10-19 22:42 ` David S. Miller
2004-10-19 22:51 ` Lee Revell
2004-10-20 0:44 ` David S. Miller
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=1098222676.23367.18.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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).