From: Nish Aravamudan <nish.aravamudan@gmail.com>
To: Olivier Croquette <ocroquette@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setitimer timer expires too early
Date: Sun, 1 May 2005 23:07:16 -0700 [thread overview]
Message-ID: <29495f1d0505012307912d6b2@mail.gmail.com> (raw)
In-Reply-To: <4273A51E.6080503@free.fr>
On 4/30/05, Olivier Croquette <ocroquette@free.fr> wrote:
> Nish Aravamudan wrote:
>
> > Perhaps not discussed before, but definitely a known issue. Check out
> > sys_nanosleep(), which adds an extra jiffy to the delay if there is
> > going to be one. My patch, which uses human-time (or at least more so
> > than currently), should not have issues like this.
>
> What would be then the most precise and reliable delaying possibility in
> the present kernel?
With Paulo's patch, everything should be ok with itimers again. The
best you can get with HZ=1000 and sleeping is 1 millisecond (ideally).
If you are ok with busy-waiting, then you get pretty arbitrary delays
(usleep(), etc.).
If you are willing to up HZ (10000 would give you 500 us resolution),
things may get better. You could also try the HRT patches (not in
mainline): http://sourceforge.net/projects/high-res-timers/
Finally, I posted my RFC for a new soft-timer subsystem based on John
Stultz's timeofday rework last week.
Good luck,
Nish
prev parent reply other threads:[~2005-05-02 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 17:24 setitimer timer expires too early Olivier Croquette
2005-04-29 19:06 ` Paulo Marques
2005-04-29 21:25 ` Nish Aravamudan
2005-04-30 15:32 ` Olivier Croquette
2005-05-02 6:07 ` Nish Aravamudan [this message]
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=29495f1d0505012307912d6b2@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocroquette@free.fr \
/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