mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Jos Hulzink <josh@stack.nl>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: udelay and nanosleep questions
Date: Sat, 21 Sep 2002 20:51:38 -0700	[thread overview]
Message-ID: <3D8D3E4A.94C19E1@mvista.com> (raw)
In-Reply-To: <20020921124235.I46546-100000@toad.stack.nl>

Jos Hulzink wrote:
> 
> 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...

You might want to check out the high-res-timers stuff.  We
will be sending this in soon for 2.5, for 2.4, see the link
below.

-g
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

      parent reply	other threads:[~2002-09-22  3:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-21 11:23 Jos Hulzink
2002-09-21 11:35 ` Russell King
2002-09-22  3:51 ` george anzinger [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=3D8D3E4A.94C19E1@mvista.com \
    --to=george@mvista.com \
    --cc=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®