On Thu, 22 May 2003 07:52:44 +0200, Mike Galbraith said:
> It does consider cpu usage though. Your run history is right there in your
> accumulated sleep_avg. Unfortunately (in some ways, fortunate in others..
> conflict) that information can be diluted down to nothing instantly by new
> input from one wakeup.
Maybe there should be a scheduler tunable that says how much it should be
diluted?
This archive was generated by hypermail 2b29 : Fri May 23 2003 - 22:00:49 EST