All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Stan Bubrouski <stan@ccs.neu.edu>, Rik van Riel <riel@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>
Subject: Re: Bad interactivity with 2.6-test9
Date: Tue, 18 Nov 2003 07:06:58 +1100	[thread overview]
Message-ID: <200311180706.58225.kernel@kolivas.org> (raw)
In-Reply-To: <1069099418.23780.2.camel@duergar>

On Tue, 18 Nov 2003 07:03 am, Stan Bubrouski wrote:
> On Mon, 2003-11-17 at 13:54, Rik van Riel wrote:
> > On Sun, 16 Nov 2003, Stan Bubrouski wrote:
> > > When I start watching a video under mplayer and have something like
> > > spamassassin doing a sa-learn in an x-term if I start the sa-learn
> > > before mplayer and then play a video, the sa-learn makes  no  progress
> > > until I switch away from mplayer (playing full screen).  After which
> > > sa-learn continues to filter through messages much faster, and even
> > > while mplayer is going is still progressing much faster than before I
> > > switched away from mplayer the first time.
> > >
> > > Very odd.  Con anyone ideas?
> >
> > Looks like scheduler starvation.  Con ?
>
> Seems like it.  I'll do some testing later to see exactly how
> consistently I can reproduce this.  I have noticed this numerous times
> all with -test9.

Usual checks. See if it happened with test6,7,8 as well as 9.
Do `vmstat 1' output to file and `top -d 1' output to file. They can tell if 
it's a dynamic priority related scheduler starvation issue.

Con


      reply	other threads:[~2003-11-17 20:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17  3:42 Bad interactivity with 2.6-test9 Stan Bubrouski
2003-11-17 18:54 ` Rik van Riel
2003-11-17 20:03   ` Stan Bubrouski
2003-11-17 20:06     ` Con Kolivas [this message]

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=200311180706.58225.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=stan@ccs.neu.edu \
    /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.