From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Paul Turner <pjt@google.com>, Andrew Hunter <ahh@google.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Andi Kleen <andi@firstfloor.org>,
Dave Watson <davejwatson@fb.com>, Chris Lameter <cl@linux.com>,
Ingo Molnar <mingo@redhat.com>, Ben Maurer <bmaurer@fb.com>,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Josh Triplett <josh@joshtriplett.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <linux@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [RFC PATCH v2 0/3] getcpu_cache system call
Date: Wed, 27 Jan 2016 11:54:40 -0500 [thread overview]
Message-ID: <1453913683-28915-1-git-send-email-mathieu.desnoyers@efficios.com> (raw)
Hi,
Here is a patchset implementing a cache for the CPU number of the
currently running thread in user-space.
Benchmarks comparing this approach to a getcpu based on system call on
ARM show a 44x speedup. They show a 14x speedup on x86-64 compared to
executing lsl from a vDSO through glibc.
I'm added a man page in the changelog of patch 1/3, which shows an
example usage of this new system call.
This patchset is sent as RFC. It applies on Linux 4.4.
Feedback is welcome,
Thanks!
Mathieu
Mathieu Desnoyers (3):
getcpu_cache system call: cache CPU number of running thread
getcpu_cache: wire up ARM system call
getcpu_cache: wire up x86 32/64 system call
MAINTAINERS | 6 ++
arch/arm/include/uapi/asm/unistd.h | 1 +
arch/arm/kernel/calls.S | 1 +
arch/arm/kernel/signal.c | 1 +
arch/x86/entry/common.c | 1 +
arch/x86/entry/syscalls/syscall_32.tbl | 1 +
arch/x86/entry/syscalls/syscall_64.tbl | 1 +
fs/exec.c | 1 +
include/linux/sched.h | 36 +++++++++++
init/Kconfig | 10 ++++
kernel/Makefile | 1 +
kernel/fork.c | 4 ++
kernel/getcpu_cache.c | 106 +++++++++++++++++++++++++++++++++
kernel/sched/sched.h | 1 +
kernel/sys_ni.c | 3 +
15 files changed, 174 insertions(+)
create mode 100644 kernel/getcpu_cache.c
--
2.1.4
next reply other threads:[~2016-01-27 16:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:54 Mathieu Desnoyers [this message]
2016-01-27 16:54 ` [RFC PATCH v2 1/3] getcpu_cache system call: cache CPU number of running thread Mathieu Desnoyers
2016-01-27 17:20 ` Josh Triplett
2016-01-27 17:24 ` Thomas Gleixner
2016-01-27 17:36 ` Mathieu Desnoyers
2016-01-27 18:02 ` Andrew Hunter
2016-01-27 18:03 ` Josh Triplett
2016-01-27 18:43 ` Mathieu Desnoyers
2016-01-27 19:16 ` Josh Triplett
2016-01-27 21:02 ` Mathieu Desnoyers
2016-01-27 21:30 ` Josh Triplett
2016-01-27 17:22 ` Thomas Gleixner
2016-01-27 17:31 ` Mathieu Desnoyers
2016-01-27 17:34 ` Thomas Gleixner
2016-01-27 17:37 ` Thomas Gleixner
2016-01-27 21:34 ` Mathieu Desnoyers
2016-01-27 22:11 ` Josh Triplett
2016-01-27 22:47 ` Mathieu Desnoyers
2016-01-28 11:12 ` Heiko Carstens
2016-01-28 13:33 ` Mathieu Desnoyers
2016-01-28 3:12 ` Alexei Starovoitov
2016-01-28 17:41 ` Mathieu Desnoyers
2016-01-27 16:54 ` [RFC PATCH v2 2/3] getcpu_cache: wire up ARM system call Mathieu Desnoyers
2016-01-27 18:19 ` Russell King - ARM Linux
2016-01-27 18:46 ` Mathieu Desnoyers
2016-01-27 23:03 ` Mathieu Desnoyers
2016-01-27 16:54 ` [RFC PATCH v2 3/3] getcpu_cache: wire up x86 32/64 " Mathieu Desnoyers
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=1453913683-28915-1-git-send-email-mathieu.desnoyers@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=ahh@google.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=bmaurer@fb.com \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=davejwatson@fb.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®