From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: CLOCK_REALTIME_RES and nanosecond resolution
Date: Tue, 08 Nov 2005 13:55:11 +1100 [thread overview]
Message-ID: <1131418511.4652.88.camel@gaston> (raw)
Hi !
I noticed that we set
#define CLOCK_REALTIME_RES TICK_NSEC /* In nano seconds. */
Unconditionally in kernel/posix-timer.c
Doesn't that mean that we'll advertise to userland (via clock_getres) a
resolution that is basically HZ ? We do get at lenght to get more
precise (up to ns) resolution in practice on many architectures but we
don't expose that to userland at all. Is this normal ?
Ben.
next reply other threads:[~2005-11-08 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 2:55 Benjamin Herrenschmidt [this message]
2005-11-08 4:16 ` Steven Rostedt
2005-11-08 9:34 ` Thomas Gleixner
2005-11-08 9:45 ` Benjamin Herrenschmidt
2005-11-08 12:56 ` Roman Zippel
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=1131418511.4652.88.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®