> As a side remark, one should note that you do not need to write
> malicious programs to observe this limitation of the CPU time
> accounting in Linux. I'm working on a realtime video processing
> application right now and it is quite hard to time, because of the
> time accounting limitations.
This is an area which _can_ be adressed cheaply in the
current code. We're already using the TSC counter for
scheduling purposes, so why not use it for near-perfect
time accounting?
I guess I'll completely give up on my scheduler changes
until there's some instrumentation available to measure
things. Besides, there are more then enough other things
that need to be done (now that the scheduling seems to
be good enough in 2.2.8, with only a superfluous
reschedule_idle() in schedule_tail()).
Finger me for more details...
cheers,
Rik -- Open Source: you deserve to be in control of your data.
+-------------------------------------------------------------------+
| Le Reseau netwerksystemen BV: http://www.reseau.nl/ |
| Linux Memory Management site: http://humbolt.geo.uu.nl/Linux-MM/ |
| Nederlandse Linux documentatie: http://www.nl.linux.org/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/