On Sat, Apr 14, 2007 at 02:02:20PM +0200, Ingo Molnar wrote: > cool. ringtest.c is intended to be used the following way: start it, it > will generate a 99% busy system (but it is using a ring of 100 tasks, > where each tasks runs for 100 msecs then sleeps for 1 msec, so every > task gets a turn every 10 seconds). If you add a pure CPU hog to the > system, for example an infinite shell loop: > while :; do :; done & > then a 'fair' scheduler would give roughly 50% of CPU time to the CPU > hog (and the ringtest.c tasks take up the other 50%).
I've queued up modifying ringtest.c to automatically spawn a CPU hog and then report aggregate CPU bandwidth of the ring and the bandwidth of the CPU hog as work to do at some point. I've no guarantee I'll get to it in a timely fashion, though. -- wli - 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/
