From: David Howells <dhowells@redhat.com>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Oleg Nesterov <oleg@tv-sign.ru>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
a.p.zijlstra@chello.nl, apw@shadowen.org,
Ingo Molnar <mingo@elte.hu>,
nickpiggin@yahoo.com.au, paulmck@linux.vnet.ibm.com,
rusty@rustcorp.com.au, Steven Rostedt <rostedt@goodmis.org>,
linux-arch@vger.kernel.org
Subject: Re: + kthread-add-a-missing-memory-barrier-to-kthread_stop.patch added to -mm tree
Date: Mon, 25 Feb 2008 13:55:50 +0000 [thread overview]
Message-ID: <7789.1203947750@redhat.com> (raw)
In-Reply-To: <b647ffbd0802231151w481fdcb5hc2a3972e7fd03f69@mail.gmail.com>
Dmitry Adamushko <dmitry.adamushko@gmail.com> wrote:
> (3)
>
> LOCK
>
> LOAD(a)
> MODIFY(b)
>
> UNLOCK
>
> and this last one is a problem. No?
I assume you meant:
LOCK
LOAD(b)
MODIFY(a)
UNLOCK
David
next prev parent reply other threads:[~2008-02-25 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 7:33 + kthread-add-a-missing-memory-barrier-to-kthread_stop.patch added to -mm tree akpm
2008-02-23 16:27 ` Oleg Nesterov
2008-02-23 17:35 ` Steven Rostedt
2008-02-23 17:54 ` Linus Torvalds
2008-02-23 18:22 ` Oleg Nesterov
2008-02-23 18:57 ` Linus Torvalds
2008-02-23 19:36 ` Oleg Nesterov
2008-02-23 19:51 ` Dmitry Adamushko
2008-02-23 20:08 ` Linus Torvalds
2008-02-23 21:03 ` [PATCH, 3rd resend] documentation: atomic_add_unless() doesn't imply mb() on failure Oleg Nesterov
2008-02-23 21:07 ` + kthread-add-a-missing-memory-barrier-to-kthread_stop.patch added to -mm tree Dmitry Adamushko
2008-02-25 13:55 ` David Howells [this message]
2008-02-23 19:41 ` Dmitry Adamushko
2008-02-23 20:02 ` Linus Torvalds
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=7789.1203947750@redhat.com \
--to=dhowells@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=dmitry.adamushko@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=oleg@tv-sign.ru \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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 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.