Hi.

Andriy Gapon wrote:
> I wonder if instead of calling statclock() multiple times (after an idle 
> period)
> we couldn't call it just with an appropriate N parameter.
> So some stats like e.g. cp_time[] could do +=N instead of ++.
> Other stats ru_ixrss need to be updated only once.
> Similarly, N could be passed further down to sched_clock() and handled there 
> too.

I think yes. It is reasonable. Initially hardclock() was also called in
a loop. It was just rewritten first because it is called more often
(more times), goes to hardware to sync time, and any way required
changes to work properly.

-- 
Alexander Motin
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[email protected]"
  • statclock(n) Andriy Gapon
    • Re: statclock(n) Alexander Motin

Reply via email to