[coyotos-dev] coyotos.sleep, sleepTill, the epoch

[Jonathan S. Shapiro]

A 0.25ms tick counter will eat 4% of the CPU **if it is implemented in
the kernel**. That goes to ~10% if it is implemented at user level.

You don't want a tick counter because you don't actually ask for time of
day 4,000 times per second. What you want is a free-running interval
counter that can be queried by the ToD implementation at need.

shap

On Mon, 2007-02-12 at 02:54 +0100, Valerio Bellizzomi wrote:
> On 09/02/2007, at 15.40, Jonathan S. Shapiro wrote:
> 
> ...
> 
> >Something you definitely do NOT want is a 1ms granularity interrupt to
> >maintain a tick counter. On current hardware this will account for a
> >measurable fraction of the machine.
> 
> To what granularity do I want ?
> 
> What fraction % ?
> 
> 
> Tick tick tick,
> val
> 
> 
> _______________________________________________
> coyotos-dev mailing list
> coyotos-dev at smtp.coyotos.org
> http://www.coyotos.org/mailman/listinfo/coyotos-dev
-- 
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100