public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Daniel Phillips <phillips@arcor.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH] O1int 0307021808 for interactivity
Date: Thu, 3 Jul 2003 22:21:55 +1000	[thread overview]
Message-ID: <200307032221.55773.kernel@kolivas.org> (raw)
In-Reply-To: <200307031346.04354.phillips@arcor.de>

On Thu, 3 Jul 2003 21:46, Daniel Phillips wrote:
> On Wednesday 02 July 2003 10:23, Con Kolivas wrote:
> > This latest patch I'm formally announcing has the base O1int changes so
> > far but includes new semantics for freshly started applications so they
> > can become interactive very rapidly even during heavy load. This
> > addresses the "slow to start new apps" evident in O1int so far.
> >
> > Please test this one and note given just how rapidly things can become
> > interactive it may have regressions in other settings.
>
> Without this patch, audio skips horribly when I drag a large window.  With
> it, audio is skipless during window dragging, so I like this patch,
> whatever it does (maybe you'd like to do a victory lap and re-explain the

Lap complete :) Theory? uh erm it's rather involved but basically instead of 
working off the accumulated sleeping ticks gathered in ten seconds it works 
on the accumulated sleeping ticks gathered till it wakes up. It has non 
linear semantics to cope with the fact that you cant accumulate 10 seconds 
worth of ticks (for example) if only 10 seconds has passed (likewise for less 
time). Also idle tasks are no longer considered fully interactive but idle 
and receive no boost or penalty. Finally they all start with some sleep ticks 
inherited by their parent as though they have been running for 1 second at 
least.

> theory?).  It's not perfect: in Mozilla, scrolling through a long page with
> the mouse still causes skipping.

I have (at least) one more trick up my sleeve which might help this, but this 
time I really do want some time to pass and more people test it (in -mm) 
before making another change.

Con


  reply	other threads:[~2003-07-03 12:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02  8:23 [PATCH] O1int 0307021808 for interactivity Con Kolivas
2003-07-03 11:46 ` Daniel Phillips
2003-07-03 12:21   ` Con Kolivas [this message]
2003-07-03 14:27     ` Daniel Phillips
2003-07-03 14:34       ` Con Kolivas
2003-07-03 16:29         ` Daniel Phillips
  -- strict thread matches above, loose matches on Subject: below --
2003-07-02  9:17 Luis Miguel Garcia
2003-07-02  9:53 ` Con Kolivas
2003-07-02 10:09   ` Luis Miguel Garcia
2003-07-02 10:12   ` Luis Miguel Garcia
2003-07-02 10:10     ` Con Kolivas

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=200307032221.55773.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    /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