public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Andreas Boman <aboman@midgaard.us>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.72 O(1) interactivity bugfix
Date: Thu, 19 Jun 2003 08:43:29 +1000	[thread overview]
Message-ID: <200306190843.29170.kernel@kolivas.org> (raw)
In-Reply-To: <1055959194.1077.21.camel@asgaard.midgaard.us>

On Thu, 19 Jun 2003 03:59, Andreas Boman wrote:
> On Wed, 2003-06-18 at 10:43, Con Kolivas wrote:
> > --BEGIN PGP SIGNED MESSAGE--
> > Hash: SHA1
> >
> > Hi Ingo, all
> >
> > While messing with the interactivity code I found what appears to be an
> > uninitialised variable (p->sleep_avg), which is responsible for all the
> > boost/penalty in the scheduler. Initialising this variable to 0 seems to
> > have made absolutely massive improvements to system responsiveness under
> > load and completely removed audio skips up to doing a make -j64 on my
> > uniprocessor P4 (beyond which swap starts being used), without changing
> > the scheduler timeslices. This seems to help all 2.4 O(1) based kernels
> > as well. Attached is a patch against 2.5.72 but I'm not sure about the
> > best place to initialise it.
>
> Applying this ontop of 2.5.72-mm1 causes more xmms/mpg321/ogg123
> skipping than with plain -mm1 here. make -j20 on my up athlon 1900+ with
> 512M ram causes extreme skipping until the make is killed. With plain
> -mm1 I may get _one_ skip at the very begining of a song during make
> -j20 (about 50% of the time). Plain -mm1 stops skipping after 10-15 sec
> of playback of a song, and even switching desktops after that doesnt
> cause skips, with or without make -j20 running (switching to/from
> desktops with apps like mozilla, evolution etc. will cause skips during
> the first 10-15 sec of a song regardless what I do it seems).
>
> Renicing xmms to -15 doesnt change anything with either kernel.

Hmm. I got too excited with the fact it improved so much on the 2.4 O(1) 
kernels that I didn't try it hard enough on the 2.5 kernels. I have had 
people quietly telling me that it isn't uninitialised, but that I am simply 
resetting it with this patch on new forked processes. It seems the extra 
changes to the 2.5 scheduler make this patch make things worse?

I need more testing of the 2.4 one as well to see if it was just my 
combination of hardware and kernel that was better with this...

Con


  reply	other threads:[~2003-06-18 22:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 14:43 [PATCH] 2.5.72 O(1) interactivity bugfix Con Kolivas
2003-06-18 17:59 ` Andreas Boman
2003-06-18 22:43   ` Con Kolivas [this message]
     [not found]     ` <1055977195.1077.41.camel@asgaard.midgaard.us>
2003-06-18 23:38       ` Con Kolivas
     [not found]         ` <1055983621.1753.23.camel@asgaard.midgaard.us>
2003-06-19  1:12           ` Con Kolivas
2003-06-19  2:00             ` Andreas Boman
2003-06-19  6:13             ` Mike Galbraith
2003-06-19  6:35               ` Con Kolivas
2003-06-19  8:11                 ` Con Kolivas
2003-06-19  7:33               ` Nick Piggin
2003-06-19  8:51                 ` Mike Galbraith
2003-06-19  8:57                   ` Nick Piggin
2003-06-19  9:00                     ` Nick Piggin
2003-06-19  9:18                     ` Mike Galbraith
2003-06-18 18:05 ` Robert Love

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=200306190843.29170.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=aboman@midgaard.us \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox