From: John <me@privacy.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Better resolution using the hrtimers infrastructure
Date: Mon, 16 Oct 2006 10:21:38 +0200 [thread overview]
Message-ID: <45334112.8070202@privacy.net> (raw)
In-Reply-To: <452DFA6D.4030300@privacy.net>
John wrote:
> I've been experimenting with the high-resolution timer subsystem on the
> x86 platform (specifically, P4 2.8 GHz) running Linux 2.6.16.28. (LAPIC
> and IOAPIC turned on, pre-emptible kernel, HZ=250)
>
> I wrote a small app to create a POSIX timer (timer_create(),
> timer_settime(), etc) that fires with a given period. The scheduling
> policy is set to SCHED_RR. After some time, the process writes the
> distribution of "elapsed time between signals" to a file, and exits. I
> then post-process this file to output average time between signals,
> standard deviation, occurences +/- 5 µs and occurences +/- 10 µs.
>
> [...]
Given the dearth of replies, I assume that linux-kernel is not the
appropriate venue for this type of question.
Could someone point to a better forum?
Regards.
next prev parent reply other threads:[~2006-10-16 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 8:18 Better resolution using the hrtimers infrastructure John
2006-10-16 8:21 ` John [this message]
2006-10-16 13:43 ` Steven Rostedt
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=45334112.8070202@privacy.net \
--to=me@privacy.net \
--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