From: Rusty Russell <rusty@rustcorp.com.au>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: Is stopmachine() preempt safe?
Date: Mon, 28 Aug 2006 09:38:55 +1000 [thread overview]
Message-ID: <1156721935.10467.1.camel@localhost.localdomain> (raw)
In-Reply-To: <10990.1156671752@ocs10w.ocs.com.au>
On Sun, 2006-08-27 at 19:42 +1000, Keith Owens wrote:
> I cannot convince myself that stopmachine() is preempt safe. What
> prevents this race with CONFIG_PREEMPT=y?
Nothing. Read side is preempt_disable. Write side is stopmachine.
I wrote it that way to avoid having to touch the scheduler. A bigger
stopmachine is possible which schedules all preempted tasks; my plan is
to write such a thing shortly, to see what it looks like.
Cheers,
Rusty.
--
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law
next prev parent reply other threads:[~2006-08-27 23:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 9:42 Is stopmachine() preempt safe? Keith Owens
2006-08-27 23:38 ` Rusty Russell [this message]
2006-08-28 2:55 ` Keith Owens
2006-08-28 6:17 ` Rusty Russell
2006-08-28 6:36 ` Keith Owens
2006-08-28 9:21 ` Rusty Russell
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=1156721935.10467.1.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=kaos@ocs.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.