From: David Miller <davem@davemloft.net>
To: tglx@linutronix.de
Cc: mikulas@artax.karlin.mff.cuni.cz, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NOHZ: local_softirq_pending with tickless plip
Date: Thu, 17 May 2007 13:29:37 -0700 (PDT) [thread overview]
Message-ID: <20070517.132937.29572252.davem@davemloft.net> (raw)
In-Reply-To: <1179399131.3764.50.camel@chaos>
From: Thomas Gleixner <tglx@linutronix.de>
Date: Thu, 17 May 2007 12:52:11 +0200
> On Wed, 2007-05-16 at 15:00 +0200, Mikulas Patocka wrote:
> > Hi
> >
> > On one of my machines with tickless kernel and plip I get messages :
>
> I bet this is a machine a P4 with Hyperthreading enabled ?
>
> > NOHZ: local_softirq_pending 08
> >
> > always when using plip (on other machine with tickless kernel and plip I
> > get no errors). Thebug happens both on 2.6.21 and 2.6.22-rc1
> >
> > This patch fixes that. Note that plip calls netif_rx neither from hardware
> > interrupt nor from ksoftirqd, so there is no one who would wake
> > ksoftirqd then. netif_tx calls only
> > __raise_softirq_irqoff(NET_RX_SOFTIRQ), which sets softirq bit, but
> > doesn't wake ksoftirqd.
>
> Dave,
>
> can we please get rid of __raise_softirq_irqoff() at all ? These micro
> optimizations are causing more trouble than they are worth.
Actually I think this is pointing out a bug, in that plip is not
invoking things in the proper context, which will likely cause
other problems :-)
I'll put this on my TODO list and look into this.
next prev parent reply other threads:[~2007-05-17 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0705161415350.10041@artax.karlin.mff.cuni.cz>
2007-05-17 10:52 ` Thomas Gleixner
2007-05-17 13:05 ` Mikulas Patocka
2007-05-17 20:29 ` David Miller [this message]
2007-05-19 21:34 ` David 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=20070517.132937.29572252.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikulas@artax.karlin.mff.cuni.cz \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®