From: Linus Torvalds <torvalds@linux-foundation.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will.deacon@arm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 5/5] locking/mcs: Relax to atomic/release semantics
Date: Sun, 20 Sep 2015 11:26:32 -0700 [thread overview]
Message-ID: <CA+55aFxCmqz-ZXB7Fs8S0+57ckseqSJtCd_JfN49Lpt5Fr2YEQ@mail.gmail.com> (raw)
In-Reply-To: <1442743911-25366-6-git-send-email-dave@stgolabs.net>
On Sun, Sep 20, 2015 at 3:11 AM, Davidlohr Bueso <dave@stgolabs.net> wrote:
> ... by using acquire semantics where appropriate As such, weakly
> ordered archs can benefit from more relaxed use of barriers when
> issuing atomics.
Again, subject is wrong.
Also, I actually think you should avoid using the word "relax", since
that actually has a separate meaning for the atomics, and it is *not*
using those relaxed semantics, and they wouldn't work anyway.
So you might as well just say something like
"locking: use acquire/release semantics"
or similar. Ok?
Linus
prev parent reply other threads:[~2015-09-20 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 10:11 [PATCH 0/5] locking: Adopt relaxed barrier semantics Davidlohr Bueso
2015-09-20 10:11 ` [PATCH 1/5] asm-generic: Add _{relaxed|acquire|release}() variants for inc/dec atomics Davidlohr Bueso
2015-09-20 10:11 ` [PATCH 2/5] locking/mutex: Relax to atomic/release semantics Davidlohr Bueso
2015-09-20 18:22 ` Linus Torvalds
2015-09-20 18:45 ` Davidlohr Bueso
2015-09-20 10:11 ` [PATCH 3/5] locking/rtmutex: Relax to acquire/release semantics Davidlohr Bueso
2015-09-20 10:11 ` [PATCH 4/5] locking/rwsem: " Davidlohr Bueso
2015-09-20 10:11 ` [PATCH 5/5] locking/mcs: Relax to atomic/release semantics Davidlohr Bueso
2015-09-20 18:26 ` Linus Torvalds [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=CA+55aFxCmqz-ZXB7Fs8S0+57ckseqSJtCd_JfN49Lpt5Fr2YEQ@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 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).