* Ingo Molnar <[email protected]> wrote:
> > The modified code is here :
> >
> > http://linux.1wt.eu/sched/orbitclock-0.2bench.tgz
> >
> > What is interesting to note is that it's easy to make X work a lot
> > (99%) by using 0 as the sleeping time, and it's easy to make the
> > process work a lot by using large values for the running time
> > associated with very low values (or 0) for the sleep time.
> >
> > Ah, and it supports -geometry ;-)
> >
> > It could become a useful scheduler benchmark !
>
> i just tried ocbench-0.3, and it is indeed very nice!
another thing i just noticed: when starting up lots of ocbench tasks
(say -x 6 -y 6) then they (naturally) get started up with an already
visible offset. It's nice to observe the startup behavior, but after
that it would be useful if it were possible to 'resync' all those
ocbench tasks so that they start at the same offset. [ Maybe a "killall
-SIGUSR1 ocbench" could serve this purpose, without having to
synchronize the tasks explicitly? ]
Ingo
-
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]
