diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2013-09-28 12:36:19 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-09-28 12:36:19 -0700 |
commit | aeebc264575f486c4cadc3f9d02f0049ae790c97 (patch) | |
tree | 154f4764d9fab0abff99bfc87271c67086f609c3 /crypto/wp512.c | |
parent | 3a126f85e015701e56240884f27f97543580d5f7 (diff) | |
parent | efc1d23b3d9af8cbff9f26677d67fb9c1b9cb792 (diff) |
Merge branch 'lockref' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
Pull s390 lockref enablement from Heiko Carstens:
"Enabling the new lockless lockref variant on s390 would have been
trivial until Tony Luck added a cpu_relax() call into the
CMPXCHG_LOOP(), with commit d472d9d98b46 ("lockref: Relax in cmpxchg
loop")
As already mentioned cpu_relax() is very expensive on s390 since it
yields() the current virtual cpu. So we are talking of several
thousand cycles. Considering this enabling the lockless lockref
variant would contradict the intention of the new semantics. And also
some quick measurements show performance regressions of 50% and more.
Simply removing the cpu_relax() call again seems also not very
desireable since Waiman Long reported that for some workloads the call
improved performance by 5%."
* 'lockref' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
s390: enable ARCH_USE_CMPXCHG_LOCKREF
lockref: use arch_mutex_cpu_relax() in CMPXCHG_LOOP()
mutex: replace CONFIG_HAVE_ARCH_MUTEX_CPU_RELAX with simple ifdef
Diffstat (limited to 'crypto/wp512.c')
0 files changed, 0 insertions, 0 deletions