From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: "Oliver Neukum" <oliver@neukum.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Use of mutex in interrupt context flawed/impossible, need advice.
Date: Thu, 22 Nov 2007 17:19:44 +0100 [thread overview]
Message-ID: <c384c5ea0711220819j2fa19430sb54139191d181c3b@mail.gmail.com> (raw)
In-Reply-To: <200711221711.39134.oliver@neukum.org>
Hello,
On Nov 22, 2007 5:11 PM, Oliver Neukum <oliver@neukum.org> wrote:
> Am Donnerstag 22 November 2007 schrieb Leon Woestenberg:
> > I would like to know why this is not so, and if someone has a cleaner
> > proposal than the "try spinlock" approach?
>
> Keep the semaphore.
>
I forgot to mention that I would like to be prepared for, and use the
-rt patch soon. I understand (maybe wrongly?) that semaphores are not
real-time pre-emptible, mutexes and spinlocks are.
Regards,
--
Leon
next prev parent reply other threads:[~2007-11-22 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 16:02 Leon Woestenberg
2007-11-22 16:11 ` Oliver Neukum
2007-11-22 16:19 ` Leon Woestenberg [this message]
2007-11-22 16:49 ` Michal Schmidt
2007-11-22 17:17 ` Arjan van de Ven
[not found] <fa.DDwTo7jhtvU2nkv268RloCrwiwc@ifi.uio.no>
2007-11-23 1:07 ` Robert Hancock
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=c384c5ea0711220819j2fa19430sb54139191d181c3b@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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
all inboxes | Powered by JetHome®