From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Aswin Chandramouleeswaran <aswin@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch,locking: Ciao arch_mutex_cpu_relax()
Date: Wed, 25 Jun 2014 08:25:11 +0200 [thread overview]
Message-ID: <20140625062510.GB4260@osiris> (raw)
In-Reply-To: <1403622415.15523.4.camel@buesod1.americas.hpqcorp.net>
On Tue, Jun 24, 2014 at 08:06:55AM -0700, Davidlohr Bueso wrote:
> On Mon, 2014-06-23 at 08:58 +0200, Peter Zijlstra wrote:
> > While I like the general idea; does anyone have a better name for this?
> > So in particular, the difference is that on s390:
> >
> > cpu_relax() - yields the vcpu
> > arch_{,mutex_}cpu_relax() - will actually spin-wait
>
> iirc Heiko had suggested cpu_relax_simple() in the past. I don't think
> it's any better or worse than arch_cpu_relax(). For s390
> cpu_relax_noyield() would perhaps be suitable, but not very descriptive
> for the rest of the archs. I'm really lacking creativity for this name.
Maybe cpu_relax_spin() ? However that doesn't sound much better as well.
next prev parent reply other threads:[~2014-06-25 6:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 18:21 [PATCH] arch,locking: Ciao arch_mutex_cpu_relax() Davidlohr Bueso
2014-06-23 6:54 ` Peter Zijlstra
2014-06-23 7:13 ` Vineet Gupta
2014-06-23 11:34 ` Peter Zijlstra
2014-06-23 6:58 ` Peter Zijlstra
2014-06-24 15:06 ` Davidlohr Bueso
2014-06-25 6:25 ` Heiko Carstens [this message]
2014-06-25 11:57 ` Linus Torvalds
2014-06-29 22:09 ` [PATCH v2] " Davidlohr Bueso
2014-08-05 13:04 ` Geert Uytterhoeven
2014-08-05 17:42 ` Davidlohr Bueso
2014-08-08 1:18 ` Davidlohr Bueso
2014-08-08 10:45 ` Guenter Roeck
2014-08-15 19:34 ` Guenter Roeck
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=20140625062510.GB4260@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox