From: Nick Piggin <piggin@cyberone.com.au>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Nick's scheduler policy
Date: Mon, 25 Aug 2003 13:05:16 +1000 [thread overview]
Message-ID: <3F497CEC.3030507@cyberone.com.au> (raw)
In-Reply-To: <1061735355.1034.2.camel@teapot.felipe-alfaro.com>
Felipe Alfaro Solana wrote:
>On Sun, 2003-08-24 at 14:35, Nick Piggin wrote:
>
>>Hi,
>>Patch against 2.6.0-test4. It fixes a lot of problems here vs
>>previous versions. There aren't really any open issues for me, so
>>testers would be welcome.
>>
>>The big change is more dynamic timeslices, which allows "interactive"
>>tasks to get very small timeslices while more compute intensive loads
>>can be given bigger timeslices than usual. This works properly with
>>nice (niced processes will tend to get bigger timeslices).
>>
>>I think I have cured test-starve too.
>>
>
>I haven't still found any starvation cases, but forking time when the
>system is under heavy load has increased considerable with respect to
>vanilla or Con's O18.1int:
>
>1. On a Konsole session, run "while true; do a=2; done"
>2. Now, try forming a new Konsole session and you'll see it takes
>approximately twice the time it takes when the system is under no load.
>
Yeah, it probably penalises parents and children too much on fork, and
doesn't penalise parents of exiting cpu hogs enough. I have noticed
this too.
>
>Also, renicing X to -20 helps X interactivity, while with Con's patches,
>renicing X to -20 makes it feel worse.
>
renicing IMO is a lot more sane in my patches, although others might
disagree. In Con's patches, when you make X -20, it gets huge timeslices.
In my version, it will get lots of smaller timeslices.
Thanks again for testing.
Nick
next prev parent reply other threads:[~2003-08-25 3:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 12:35 [PATCH] Nick's scheduler policy Nick Piggin
2003-08-24 14:29 ` Felipe Alfaro Solana
2003-08-25 3:05 ` Nick Piggin [this message]
2003-08-25 22:30 ` Bill Davidsen
2003-08-24 16:55 ` Martin J. Bligh
2003-08-25 3:00 ` Nick Piggin
2003-08-25 10:41 ` [PATCH] Nick's scheduler policy v7 Nick Piggin
2003-08-25 11:03 ` Felipe Alfaro Solana
2003-08-25 14:36 ` Måns Rullgård
2003-08-26 3:24 ` Martin J. Bligh
2003-08-26 4:04 ` Nick Piggin
2003-08-26 9:44 ` Yaroslav Rastrigin
2003-08-27 9:28 ` Mike Galbraith
2003-08-25 3:27 ` [PATCH] Nick's scheduler policy Randy.Dunlap
2003-08-25 3:36 ` Nick Piggin
2003-08-26 3:16 ` Mike Fedyk
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=3F497CEC.3030507@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=felipe_alfaro@linuxmail.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