From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] softirq-2.4.5-B0
Date: 27 May 2001 23:17:30 +0200 [thread overview]
Message-ID: <oup4ru6bifp.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <15120.16986.610478.279574@pizda.ninka.net.suse.lists.linux.kernel> <Pine.LNX.4.33.0105271020310.1667-200000@localhost.localdomain.suse.lists.linux.kernel> <15121.21054.657593.830199@pizda.ninka.net.suse.lists.linux.kernel>
In-Reply-To: "David S. Miller"'s message of "27 May 2001 21:20:33 +0200"
"David S. Miller" <davem@redhat.com> writes:
> > the attached softirq-2.4.5-B0 patch fixes this problem by calling
> > do_softirq() from local_bh_enable() [if the bh count is 0, to avoid
> > recursion].
>
> Yikes! I do not like this fix.
>
> I'd rather local_bh_enable() not become a more heavy primitive.
>
> I know, in one respect it makes sense because it parallels how
> hardware interrupts work, but not this thing is a function call
> instead of a counter bump :-(
>
> Any other ideas how to zap this?
I think the right way to fix it is to do a final atomic check for softirqs
when the kernel is exited. To be atomic this check neededs to be done with
interrupts off until the kernel exited. I just implemented a very similar way
into the x86-64 kernel (which needs to turn off interrupts for kernel anyways
for other reasons, this just extends the cli area a bit). The same atomic
check is needed for race free check of need_schedule (which is still racy
on plain i386).
-Andi
next parent reply other threads:[~2001-05-27 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15120.16986.610478.279574@pizda.ninka.net.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0105271020310.1667-200000@localhost.localdomain.suse.lists.linux.kernel>
[not found] ` <15121.21054.657593.830199@pizda.ninka.net.suse.lists.linux.kernel>
2001-05-27 21:17 ` Andi Kleen [this message]
2001-05-27 21:19 ` Ingo Molnar
2001-05-26 23:55 [patch] severe softirq handling performance bug, fix, 2.4.5 David S. Miller
2001-05-27 19:00 ` [patch] softirq-2.4.5-B0 Ingo Molnar
2001-05-27 19:15 ` David S. Miller
2001-05-27 19:19 ` Ingo Molnar
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=oup4ru6bifp.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®