Re: sched_clock() uses are broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2006-05-08 at 14:46 +1000, Nick Piggin wrote:
> It should either get ripped out, or perhaps converted to use jiffies
> until a sane high resolution, low overhead scheme is developed (if
> ever). And that would exclude something that does this accounting in
> fastpaths for the 99.99% of processes that never use it.

The accounting is really light compared to the interactivity part.  That
doesn't need to be in the fast path, and in my tree it isn't.

FWIW (0), yy tree is missing every last shred of the interactivity code,
and not missing it one bit.

[[email protected]]:> diffstat xx
 sched.c |  480
+++++++++++++++++++++++++++++-----------------------------------
 1 files changed, 219 insertions(+), 261 deletions(-)

And that's with full throttling, and absolute starvation proofing.

Ho hum.  Back to work on my never-going-anywhere-but-fun tree :)

	later,

	-Mike (shutting the hell up now;)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux