Re: [9fans] sleep(2) historical question

[arnold@skeeve.com]

> Seems best to get rid of the fixed 100Hz clock and allow as
> fine a timer resolution (& accuracy) as a particular CPU +
> kernel combination can do.

So what this argues for is a query interface - hello mr. kernel, what can
you and your hardware do?  In whatever units make sense. Then userspace
can do the calculation it needs and ask for the sleep time that it will
know the kernel can really supply.

Erik's problem boils down to "the kernel knows what it can do and is
quite capable but i can't get it at from user space".  So (a) make
the information availble and (b) let user space figure it out. Classic
separation of mechanism from policy.

At least, that what it looks like to me. :-)

Arnold