All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Mike Galbraith <efault@gmx.de>, Daniel Gryniewicz <dang@fprintf.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Subject: Re: patch O1int for 2.5.73 - interactivity work
Date: Thu, 26 Jun 2003 07:43:10 +1000	[thread overview]
Message-ID: <200306260743.10999.kernel@kolivas.org> (raw)
In-Reply-To: <5.2.0.9.2.20030625222455.00cf33f0@pop.gmx.net>

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


  reply	other threads:[~2003-06-25 21:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 16:09 patch O1int for 2.5.73 - interactivity work Con Kolivas
2003-06-25 19:00 ` Mike Galbraith
2003-06-25 19:34   ` Daniel Gryniewicz
2003-06-25 20:33     ` Mike Galbraith
2003-06-25 21:43       ` Con Kolivas [this message]
2003-06-25 21:53 ` Felipe Alfaro Solana
2003-06-25 23:10   ` Andy Pfiffer
2003-06-25 23:39     ` Con Kolivas
2003-06-26 20:16 ` Diego Calleja García

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200306260743.10999.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=dang@fprintf.net \
    --cc=efault@gmx.de \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.