public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH]O15int for interactivity
Date: Sat, 16 Aug 2003 06:10:07 +0200	[thread overview]
Message-ID: <1061007006.11207.23.camel@nosferatu.lan> (raw)
In-Reply-To: <200308122226.11557.kernel@kolivas.org>

[-- Attachment #1: Type: text/plain, Size: 2804 bytes --]

On Tue, 2003-08-12 at 15:22, Con Kolivas wrote:
> This patch addresses the problem of tasks that preempt their children when 
> they're forking, wasting cpu cycles until they get demoted to a priority where 
> they no longer preempt their child. Although this has been said to be a design 
> flaw in the applications, it can cause sustained periods of starvation due to 
> this coding problem, and the more I looked, the more examples I found of this 
> happening.
> 
> Tasks now cannot preempt their own children. This speeds up the startup of 
> child applications (eg pgp signed email).
> 
> This change has allowed tasks to stay at higher priority for much longer so 
> the sleep avg decay of high credit tasks has been changed to match the rate of 
> rise during periods of sleep (which I wanted to do originally but was limited 
> by the first problem). This makes for much more sustained interactivity at 
> extreme loads, and much less X jerkiness.
> 

Ok, finally had the chance to test O15.

Seems ok this side now with HT enabled.  I did a few tests and here
is just briefly some notes:

1)  It does take a bit longer to compile anything when the system is
    under load.  Roughly with two make -j{6,12}s going, with mm1
    and about 1 second, and with bk3 and O15 about two seconds.  I
    did not run too many passes on the bk3&O15 combination, so could
    be just some or other change in environment.  Non issue for me.

2)  XMMS/whatever still do not skip (nothing different from vanilla
    bk[13].

3)  The only major difference now between vanilla bk, and bk3+O15 or
    mm[12] and O15, is that doing the 'window wiggle test' (*g*) do
    not start to jerk after about 10 seconds as in vanilla.  It is
    either way of no significance to me, as I do not in general do
    anything that I can think of that simulate this.  With vanilla
    though, response is there immediately if the window is let go of.

4)  The evolution thread doing expunging (pop3 side) when finished
    getting mail do seem to take a bit longer.  Guess it could be
    similar to the wine issues others have seen, but once again no
    real show stopper for me (I do expect some loss in response if
    there is high load).

5)  On bk3+O15 it seems like load is a tad higher for the same
    type of tests (23-26 with vanilla, 23-28 with mm, and about
    25-30 with vanilla bk3+o13).  I guess it might be some changes
    between bk3 and mm that your stuff have a minor dependency on,
    or changes from bk1 to bk3, as bk1 was what I used for testing
    without O15.

All in all, mouse is fine, mozilla do not 'pause'/whatever when
changing tabs/scrolling (both O15 and vanilla), XMMS do not
skip, etc.


Regards,

-- 

Martin Schlemmer




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-08-16  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12 12:26 [PATCH]O15int for interactivity Con Kolivas
2003-08-12 12:36 ` Måns Rullgård
2003-08-12 14:00   ` Felipe Alfaro Solana
2003-08-12 14:04   ` Con Kolivas
2003-08-14  2:44 ` Wes Janzen
2003-08-14  2:54   ` Con Kolivas
2003-08-16  4:10 ` Martin Schlemmer [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=1061007006.11207.23.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox