From: Matt Mackall <mpm@selenic.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: William Lee Irwin III <wli@holomorphy.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH] new scheduler policy
Date: Tue, 19 Aug 2003 00:15:33 -0500 [thread overview]
Message-ID: <20030819051533.GL16387@waste.org> (raw)
In-Reply-To: <3F4192AD.1020305@cyberone.com.au>
On Tue, Aug 19, 2003 at 12:59:57PM +1000, Nick Piggin wrote:
>
>
> Nick Piggin wrote:
>
> >
> >
> >William Lee Irwin III wrote:
> >
> >>On Tue, Aug 19, 2003 at 11:53:01AM +1000, Nick Piggin wrote:
> >>
> >>>As per the latest trend these days, I've done some tinkering with
> >>>the cpu scheduler. I have gone in the opposite direction of most
> >>>of the recent stuff and come out with something that can be nearly
> >>>as good interactivity wise (for me).
> >>>I haven't run many tests on it - my mind blanked when I tried to
> >>>remember the scores of scheduler "exploits" thrown around. So if
> >>>anyone would like to suggest some, or better still, run some,
> >>>please do so. And be nice, this isn't my type of scheduler :P
> >>>It still does have a few things that need fixing but I thought
> >>>I'd get my first hack a bit of exercise.
> >>>Its against 2.6.0-test3-mm1
> >>>
> >>
> >>Say, any chance you could spray out a brief explanation of your new
> >>heuristics?
> >>
> >
> >Oh alright. BTW, this one's not for your big boxes yet! It does funny
> >things with timeslices. But they will be (pending free time) made much
> >more dynamic, so it should _hopefully_ context switch even less than
> >the normal scheduler in a compute intensive load.
> >
> >OK. timeslices: they are now dynamic. Full priority tasks will get
> >100ms, minimum priority tasks 10ms (this is what needs fixing, but
> >should be OK to test "interactiveness")
> >
> >interactivity estimator is gone: grep -i interactiv sched.c | wc -l
> >gives 0.
> >
> >priorities are much the same, although processes are supposed to be
> >able to change priority much more quickly.
> >
> >backboost is back. that is what (hopefully) prevents X from starving
> >due to the quickly changing priorities thing.
>
> And lack of interactivity estimator.
You forgot to mention fork() splitting its timeslice 2/3 to 1/3 parent
to child.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-08-19 5:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 1:53 [CFT][PATCH] new scheduler policy Nick Piggin
2003-08-19 2:35 ` William Lee Irwin III
2003-08-19 2:46 ` Nick Piggin
2003-08-19 2:59 ` Nick Piggin
2003-08-19 5:15 ` Matt Mackall [this message]
2003-08-19 5:34 ` Nick Piggin
2003-08-19 5:45 ` Matt Mackall
2003-08-19 10:24 ` Mike Galbraith
2003-08-19 13:40 ` Nick Piggin
2003-08-19 18:49 ` Mike Galbraith
2003-08-20 2:13 ` William Lee Irwin III
2003-08-25 13:47 ` Haoqiang Zheng
2003-08-25 14:03 ` Nick Piggin
2003-08-25 15:11 ` Haoqiang Zheng
2003-09-02 14:25 ` Pavel Machek
2003-09-08 13:40 ` Alan Cox
2003-09-08 14:20 ` Haoqiang Zheng
2003-09-08 14:28 ` Alan Cox
2003-09-08 15:10 ` Haoqiang Zheng
2003-08-22 8:55 ` Roger Luethi
2003-08-22 13:08 ` Nick Piggin
2003-08-22 15:11 ` Roger Luethi
2003-08-23 0:22 ` Nick Piggin
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=20030819051533.GL16387@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=wli@holomorphy.com \
/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