From: Matthias Urlichs <smurf@smurf.noris.de>
To: Rob Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about preempt_disable()
Date: Mon, 8 Dec 2003 17:31:27 +0100 [thread overview]
Message-ID: <200312010703.19113@smurf.noris.de> (raw)
In-Reply-To: <1070250821.1158.45.camel@localhost>
Hi,
Rob Love wrote:
> Further, on uniprocessor systems, we don't have deadlocks so it is the
> preempt_disable() that actually ensures concurrency is prevented in the
> critical region.
>
We don't have _spin_locks.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@debian.org
Disclaimer: The quote was selected randomly. Really. | http://smurf.debian.net
- -
I don't care how poor and inefficient a country is; they like to run their
own business. I know men that would make my wife a better husband than I am;
but, darn it, I'm not going to give her to 'em.
-- Will Rogers
next prev parent reply other threads:[~2003-12-08 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 0:59 question about preempt_disable() Chris Peterson
2003-11-30 17:39 ` Matthias Urlichs
2003-12-01 3:53 ` Rob Love
2003-12-08 16:31 ` Matthias Urlichs [this message]
2003-12-03 23:12 ` George Anzinger
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=200312010703.19113@smurf.noris.de \
--to=smurf@smurf.noris.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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).