Alex Riesen wrote:
Why don't you just use nanosleep(2) (or usleep)?
I can think of one main reason...existing code. Also, nanosleep()
rounds up excessively in many kernel versions, so that a request to
sleep for less than 1 tick ends up sleeping for 2 ticks.
The select() man page explicitly mentions this usage;
"Some code calls select with all three sets empty, n zero, and a
non-null timeout as a fairly portable way to sleep with subsecond
precision."
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]