From: Robert Love <rml@tech9.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: interrupt checks for spinlocks
Date: 03 Nov 2002 22:01:24 -0500 [thread overview]
Message-ID: <1036378887.750.96.camel@phantasy> (raw)
In-Reply-To: <20021104014224.GR23425@holomorphy.com>
On Sun, 2002-11-03 at 20:42, William Lee Irwin III wrote:
> I'll go figure out why before posting a follow-up. This is not doing
> what I wanted it to because the only one I originally wanted was (1),
> having to do with interrupt-time recursion on rwlocks and writer
> starvation caused by it.
You can do #1, but you need to figure out if your interrupt is the only
interrupt using the lock or not (possibly hard).
In other words, a lock unique to your interrupt handler does not need to
disable interrupts (since only that handler can grab the lock and it is
disabled).
If other handlers can grab the lock, interrupts need to be disabled.
So a test of irqs_disabled() would show a false-positive in the first
case. No easy way to tell..
Robert Love
next prev parent reply other threads:[~2002-11-04 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1036362421.16883.linux-kernel2news@redhat.com>
[not found] ` <200211040028.gA40S8600593@devserv.devel.redhat.com>
[not found] ` <20021104002813.GZ16347@holomorphy.com>
2002-11-04 0:42 ` interrupt checks for spinlocks Pete Zaitcev
2002-11-04 0:53 ` William Lee Irwin III
2002-11-04 1:18 ` Robert Love
2002-11-04 1:42 ` William Lee Irwin III
2002-11-04 3:01 ` Robert Love [this message]
2002-11-04 3:04 ` William Lee Irwin III
2002-11-04 3:22 ` William Lee Irwin III
2002-11-04 3:36 ` Zwane Mwaikambo
2002-11-03 22:08 William Lee Irwin III
2002-11-04 0:15 ` Davide Libenzi
2002-11-04 0:39 ` William Lee Irwin III
2002-11-04 1:39 ` Davide Libenzi
2002-11-04 1:39 ` William Lee Irwin III
2002-11-04 5:18 ` Randy.Dunlap
2002-11-04 15:47 ` Davide Libenzi
2002-11-04 13:31 ` Alan Cox
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=1036378887.750.96.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
--cc=zaitcev@redhat.com \
/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