i'm curious, what better do you need than the very detailed comment
quoted above? Which bit of "this latency value is not the same as the
concept of timeslice length" is difficult to understand? The timeslices
of tasks (i.e. the time they spend on a CPU without scheduling away) is
_not_ maintained directly in CFS as a per-task variable that can be
"cleared", it's not the metric that drives scheduling. Yes, of course
CFS too "slices up CPU time", but those slices are not the per-task
variables of traditional schedulers and cannot be 'cleared'.
wrong again. That is a function, not a variable to be cleared. (Anyway,
the noise/signal ratio is getting increasingly high in this thread with
no progress in sight, so i cannot guarantee any further replies -
possibly others will pick up the tab and explain/discuss any other
questions that might come up. Patches are welcome of course.)
Ingo
-