> > > Now dbench (or any task) is in kernel space for too long. The CPU time
> > > xmms needs will of course still be given, but _too late_. Its just not
> > > a cpu resource problem, its a timing problem. xmms needs x units of CPU
> > > every y units of time. Just getting the x whenever is not enough.
> >
> > Yep, with
> >
> > x = 60msec
> > y = 600msec
>
> How are you arriving at that y? On what system?
Toshiba sattelite notebook. I remember being able to ^Z splay process
playing mp3, and bg-ing it in time not to skip. That means that y is
at least 300msec or so.
[I wanted to retry it on k6/400 with sblive and mpg123 (not splay) and
could not do the trick.]
Pavel
-- Casualities in World Trade Center: 6453 dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/