Re: why kernel implement "udelay" by cpu instructions?

From: loody
Date: Tue Nov 03 2009 - 21:19:59 EST


2009/11/2 Rik van Riel <riel@xxxxxxxxxx>:
> On 11/01/2009 10:13 PM, loody wrote:
>> Dear all:
>> I find the kernel use cpu instruction to implement the udelay function
>> as keeping decrease a big counter by 1.
>> If I search the right place in kernel, why kernel does so?
> Because udelay is used in places where the kernel cannot
> use other mechanisms, eg. because interrupts are blocked
> or the current process cannot be scheduled out.

Or the only way to support udelay is using CPU instruction to do the counting?
I find something interesting; kernel has msleep, but it doesn't have usleep.
Does that mean the minimum time kernel can react is msecond instead of usecond?
so if users want to count useconds, they have to do the busy waiting,
execute some looping assembly instructions?

If my consumption is correct, where I can find the evidence?
BTW, does Hz has anything related to kernel timing?
>From the comment in the kernel, it says
Hz: clock ticks generated per second
Does that mean the kernel will get #Hz timer interrupts per second?
Whz the value of Hz is 100?
if the minimum reaction time of kernel is msecond, the value of Hz
should be 1000, right?

>> the precision will be different if cpu runs faster or slower, right?
> At bootup the kernel measures the delay loop speed of
> each CPU.  CPU frequency scaling might make the loop

would you please let me know where the source code is?
(measuring loop speed of cpu and scale cpu frequency)

> run slower at times, but that is okay because udelay
> simply specifies a *minimum* delay.
> This is true even on systems without frequency scaling,
> because the udelay loop could be interrupted by an
> interrupt, an NMI or by having the CPU trap into SMM
> mode and execute code there.
appreciate your kind help :)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at