From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] Wire up lockless lockrefs for ARM
Date: Thu, 3 Oct 2013 19:17:31 +0100 [thread overview]
Message-ID: <1380824254-22337-1-git-send-email-will.deacon@arm.com> (raw)
Hello,
This is version two of the patch I originally posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-September/200109.html
The main changes since then are:
* Separate cmpxchg64 from atomic64_cmpxchg, so we can implement a
barrier-less version.
* Use this new barrier-less function to implement cmpxchg64_relaxed
* Finally, use cmpxchg64_relaxed to optimise cmpxchg64_local and
implement lockless lockrefs.
This results in ~100% improvement when running Linus's t.c test
(essentially stating a file in a loop for 10 seconds).
Feedback welcome,
Will
Will Deacon (3):
ARM: cmpxchg: implement barrier-less cmpxchg64_local
ARM: cmpxchg: implement cmpxchg64_relaxed
ARM: lockref: add support for lockless lockrefs using cmpxchg64
arch/arm/Kconfig | 1 +
arch/arm/include/asm/cmpxchg.h | 58 ++++++++++++++++++++++++++++++++---------
arch/arm/include/asm/spinlock.h | 8 ++++--
3 files changed, 53 insertions(+), 14 deletions(-)
--
1.8.2.2
next reply other threads:[~2013-10-03 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 18:17 Will Deacon [this message]
2013-10-03 18:17 ` [PATCH v2 1/3] ARM: cmpxchg: implement barrier-less cmpxchg64_local Will Deacon
2013-10-03 18:17 ` [PATCH v2 2/3] ARM: cmpxchg: implement cmpxchg64_relaxed Will Deacon
2013-10-03 18:17 ` [PATCH v2 3/3] ARM: lockref: add support for lockless lockrefs using cmpxchg64 Will Deacon
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=1380824254-22337-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).