From: Greg KH <gregkh@linuxfoundation.org>
To: chi wu <wuchi.zero@gmail.com>
Cc: alexios.zavras@intel.com, allison@lohutok.net, armijn@tjaldur.nl,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/klist: Remove mb() before wake_up_process
Date: Wed, 15 Jun 2022 08:19:25 +0200 [thread overview]
Message-ID: <Yql57cL4aFbnykfL@kroah.com> (raw)
In-Reply-To: <CA+tQmHAJbqDenRE47OacSurF5HZ-XWHu6dRBf+A=UqbhiLomAA@mail.gmail.com>
On Wed, Jun 15, 2022 at 11:30:51AM +0800, chi wu wrote:
> Greg KH <gregkh@linuxfoundation.org> 于2022年6月14日周二 22:58写道:
> >
> > On Tue, Jun 14, 2022 at 10:44:43PM +0800, wuchi wrote:
> > > Function wake_up_process always executes a general memory barrier,
> > > so remove the mb() before it.
> >
> > Really? On all systems? I do not see that, where does it happen?
> >
> As I understand it, it is on all systems. Please help correct the
> mistake, thanks.
>
> 1. Follow Documentation/memory-barriers.txt line 2128 ~ 2278,
> especially line 2187 ~ 2202 snippet:
> A general memory barrier is executed by wake_up() if it wakes
> something up.
> If it doesn't wake anything up then a memory barrier may or may not be
> executed; you must not rely on it.
So as the documentation states, it might not be there, so if you have to
have a memory barrier, you must not rely on this function to provide it.
So unless you have testing proof otherwise, the code should be correct
as-is.
thanks,
greg k-h
prev parent reply other threads:[~2022-06-15 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:44 [PATCH] lib/klist: Remove mb() before wake_up_process wuchi
2022-06-14 14:58 ` Greg KH
2022-06-15 3:30 ` chi wu
2022-06-15 6:19 ` Greg KH [this message]
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=Yql57cL4aFbnykfL@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=armijn@tjaldur.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=wuchi.zero@gmail.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 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.