From: Jos Hulzink <josh@stack.nl>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: udelay and nanosleep questions
Date: Sat, 21 Sep 2002 13:23:10 +0200 (CEST) [thread overview]
Message-ID: <20020921124235.I46546-100000@toad.stack.nl> (raw)
Hi,
Talking about kernel driver programming:
1) Can I rely on udelay(1) ? i.e. is the resolution high enough to wait at
least 1 microsecond given it returns normally ? I know the actual
implementation is platform / cpu dependant, so maybe I should ask: Should
I be able to rely on udelay(1) ?
2) With the highspeed CPUs these days, the implementation of sys_nanosleep
(in kernel/timer.c) for realtime processes:
sys_nanosleep {udelay ((nsec+999)/1000}
is rather low-res. Time for something new ? sys_nanosleep seems not the
call to make for in-kernel accurate delays, for it schedules a timeout
instead of doing a busy wait. My driver needs 250 ns delays, is there a
more accurate way than udelay(1) ? It is a pity to waste 4x more
clockcycli than needed.
3) Usleep and friends seem not to care about speedstepping technologies.
Shouldn't we care, at least for in-kernel and realtime process waits ?
True, you are an idiot when running realtime processes on a speedstep
enabled CPU, but still...
Jos
next reply other threads:[~2002-09-21 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-21 11:23 Jos Hulzink [this message]
2002-09-21 11:35 ` Russell King
2002-09-22 3:51 ` george anzinger
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=20020921124235.I46546-100000@toad.stack.nl \
--to=josh@stack.nl \
--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®