Re: New "timeout" api, to replace callout
In message <20071202055031.A8107@xorpc.icir.org>, Luigi Rizzo writes:
>This is why i suggest having a 'scale' that can represent '1 tick'
>(and also don't depend on TIMEOUT_MSEC == 1000 and so on, but keep
>them opaque and require that the client code uses one of the supported
Using a deadline timer based in the HPET, the timeout can be scheduled
to any 1/14318181th of a second and there will be no concept of "a
tick" as we know it now.
Clients should say how often they want to be called, and they should
express it in terms of time, not based on some implementation detail
of a historical implementation of the scheduler.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[email]phk@FreeBSD.ORG[/email] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
[email]firstname.lastname@example.org[/email] mailing list
To unsubscribe, send any mail to "email@example.com"