Re: Possible spin-problem in nanosleep()

[Alan Cox]

For most platforms the scheduler measured busy/idle time is from the
timer tick. That means its sampled so you are limited to accurate
information on sleep/wake changes occuring at 1/2 the clock rate or
less.

Alan

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