From: Andy Lutomirski <luto@amacapital.net>
To: linux-kernel@vger.kernel.org, Kumar Sundararajan <kumar@fb.com>,
john stultz <johnstul@us.ibm.com>, Arun Sharma <asharma@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@amacapital.net>
Subject: [RFC 0/2] ABI for clock_gettime_ns
Date: Mon, 12 Dec 2011 17:26:36 -0800 [thread overview]
Message-ID: <cover.1323739287.git.luto@amacapital.net> (raw)
On x86-64, clock_gettime is so fast that the overhead converting to and
from nanoseconds is non-negligible. clock_gettime_ns is a different
interface that is potentially faster. If people like the ABI, I'll
implement an optimized version.
For the git-inclined, this series is at
https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=shortlog;h=refs/heads/timing/clock_gettime_ns/rfc_v1
Andy Lutomirski (2):
Add clock_gettime_ns syscall
x86-64: Add __vdso_clock_gettime_ns vsyscall
arch/x86/include/asm/unistd_64.h | 2 +
arch/x86/vdso/vclock_gettime.c | 70 +++++++++++++++++++++++++++++---------
arch/x86/vdso/vdso.lds.S | 7 ++++
include/linux/syscalls.h | 2 +
kernel/posix-timers.c | 29 ++++++++++++++++
5 files changed, 94 insertions(+), 16 deletions(-)
--
1.7.7.4
next reply other threads:[~2011-12-13 1:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 1:26 Andy Lutomirski [this message]
2011-12-13 1:26 ` [RFC 1/2] Add clock_gettime_ns syscall Andy Lutomirski
2011-12-13 3:32 ` Richard Cochran
2011-12-13 1:26 ` [RFC 2/2] x86-64: Add __vdso_clock_gettime_ns vsyscall Andy Lutomirski
2011-12-13 3:24 ` [RFC 0/2] ABI for clock_gettime_ns Richard Cochran
2011-12-13 3:43 ` john stultz
2011-12-13 7:09 ` Andy Lutomirski
2011-12-14 7:46 ` Richard Cochran
2011-12-14 16:48 ` john stultz
2011-12-14 17:15 ` Andy Lutomirski
2011-12-14 17:31 ` john stultz
2011-12-14 18:37 ` Richard Cochran
2011-12-14 18:30 ` Richard Cochran
2011-12-14 19:07 ` john stultz
2011-12-14 19:20 ` Andy Lutomirski
2011-12-14 21:34 ` john stultz
2011-12-15 11:35 ` Richard Cochran
2011-12-22 12:03 ` Richard Cochran
2011-12-24 5:59 ` Andy Lutomirski
2011-12-24 6:50 ` Richard Cochran
2011-12-25 4:06 ` Andy Lutomirski
2011-12-14 7:20 ` Richard Cochran
2011-12-14 16:23 ` john stultz
2011-12-14 18:21 ` Richard Cochran
2011-12-14 18:57 ` john stultz
2012-01-07 19:51 ` Richard Cochran
2011-12-21 0:50 ` Arun Sharma
2011-12-21 1:07 ` Andy Lutomirski
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=cover.1323739287.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=asharma@fb.com \
--cc=johnstul@us.ibm.com \
--cc=kumar@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome