Messages in this thread | | | From | Con Kolivas <> | Subject | Re: patch O1int for 2.5.73 - interactivity work | Date | Thu, 26 Jun 2003 07:43:10 +1000 |
| |
On Thu, 26 Jun 2003 06:33, Mike Galbraith wrote: > At 03:34 PM 6/25/2003 -0400, Daniel Gryniewicz wrote: > >On Wed, 2003-06-25 at 15:00, Mike Galbraith wrote: > > > At 02:09 AM 6/26/2003 +1000, Con Kolivas wrote: > > > >I'm still working on something for the "xmms stalls if started during > > > > very heavy load" as a different corner case. > > > ><snip scheduler suggestion> > > > > > Just a couple random thoughts, both of which I can see problems with > > > ;-) > > > >At least on 2.4 (I use 21-ck3), it appears to be I/O starvation that > >gets xmms, not scheduler starvation. When xmms skips for me, there's > >load, but there's also usually some idle time. The common thread seems > >to be heavy I/O on the drive xmms is using, possibly combined with a > >(formerly?) interactive process (evolution rebuilding my LKML index, for > >example) doing the disk I/O. Because of the assorted I/O scheduler > >changes in 2.5, this is unlikley to be the problem there. > > Ahah. I thought Con was referring to the delay at new song, new task > starting at priority 20 while things higher are using the cpu. Yeah, your > skips sound like xmms is just running out of buffered data.
No, Mike's right. If you do a make -j32 and then start up xmms, xmms seems to want to burn off some cpu when it first starts, and _then_ starts sleeping regularly; so it starts as a cpu hog for a short while and then sleeps. This makes is bloody hard for the scheduler to do the right thing to it since it gets treated as a cpu hog initially, meaning it will take forever to burn off that cpu time necessary when all other cpu hogs are also running.
Con
- 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/
| |