public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Mike Galbraith <efault@gmx.de>
Cc: linux-kernel@vger.kernel.org,
	Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
	Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: patch-O1int-0306281420 for 2.5.73 interactivity
Date: Mon, 30 Jun 2003 20:16:21 +1000	[thread overview]
Message-ID: <200306302016.21123.kernel@kolivas.org> (raw)
In-Reply-To: <5.2.0.9.2.20030630094946.00cfb000@pop.gmx.net>

On Mon, 30 Jun 2003 17:57, Mike Galbraith wrote:
> Greetings,
>
> At 03:35 PM 6/30/2003 +1000, Con Kolivas wrote:
> >Summary:
> >A patch to reduce audio skipping and X jerking under load.
>
> I took it out for a quick spin.  It kills thud graveyard dead.  That's the
> good news, now for the bad ;-)  With a make -j5 running, kasteroids
> stutters enough to be pretty annoying.  The patched kernel is making
> booboos wrt cc1's priority often enough to nail kasteroids pretty
> hard.  The mouse pointer also jerks around quite a bit,...

Consider it not optimised yet. The workings are still evolving but are now 
close. It errs on the too-easy to get a bonus in the early ms after an app 
has started at the moment.

>
> >It's looking seriously like I'm talking to myelf here, but just in case
> > there are lurkers testing this patch, there's a big bug that made it
> > think jiffy wraparound was occurring so interactive tasks weren't
> > receiving the boost they deserved. Here is a patch with the fix in.
> >
> >How to use if you're still thinking of testing:
> >Use with Hz 1000, and use the granularity patch I posted as well for
> >smoothing
> >X off.
>
> ...but I'm not using that, because I wanted to see the pure effects of this
> patch.

Good point. If it's going to be developed properly it should only include what 
is likely to be used with it.

Con


  reply	other threads:[~2003-06-30  9:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-28  5:16 patch-O1int-0306281420 for 2.5.73 interactivity Con Kolivas
2003-06-28 16:30 ` Con Kolivas
2003-06-28 17:22   ` Martin Schlemmer
2003-06-29  1:25     ` Con Kolivas
2003-06-28 18:22   ` Felipe Alfaro Solana
2003-06-28 18:02 ` Felipe Alfaro Solana
2003-06-28 20:26 ` pat erley
2003-06-28 22:45   ` Roberto Orenstein
2003-06-29  1:32     ` Con Kolivas
2003-06-29  4:57       ` Con Kolivas
2003-06-30  5:35         ` Con Kolivas
2003-06-30  7:49           ` Andrew Morton
2003-06-30  7:57           ` Mike Galbraith
2003-06-30 10:16             ` Con Kolivas [this message]
2003-06-30 10:59               ` Mike Galbraith
2003-06-30  9:02           ` Felipe Alfaro Solana
2003-06-30  9:39           ` Marc-Christian Petersen
2003-06-30  9:47             ` Andrew Morton
2003-06-30 10:10               ` Marc-Christian Petersen
2003-06-30 10:17                 ` Andrew Morton
2003-06-30 21:05                   ` Marc-Christian Petersen
2003-06-30 12:21             ` Mike Galbraith
2003-06-30 13:38               ` Con Kolivas
2003-06-30 21:09                 ` Marc-Christian Petersen
2003-06-30 18:46               ` Davide Libenzi

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=200306302016.21123.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=efault@gmx.de \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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