public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Con Kolivas <kernel@kolivas.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] CPU scheduler: Simplified interactive bonus mechanism
Date: Thu, 29 Dec 2005 09:02:06 +0100	[thread overview]
Message-ID: <20051229080206.GA22814@elte.hu> (raw)
In-Reply-To: <43B35D43.40902@bigpond.net.au>


* Peter Williams <pwil3058@bigpond.net.au> wrote:

> > So, as Con seems to imply, it is JASW (just another scheduler
> > rewrite).
> 
> Not a rewrite just some major surgery to one small part (at least when 
> compared to nicksched, staircase and the SPA schedulers).  This 
> doesn't effect the run queue structure or the load balancing 
> mechanisms.  Or, for that matter, even the bonus mechanism itself 
> other than the calculation of the bonus as the way the bonus is 
> applied once calculated is unchanged.

given the experience, i'm quite reluctant to do that. We should rather 
concentrate on trying to fix the rare odd case that gets misjudged, than 
trying to invent totally new mechanism that happen to get _that_ case 
right. (and most likely get alot of other cases wrong.)

	Ingo

  reply	other threads:[~2005-12-29  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-28  6:24 [RFC] CPU scheduler: Simplified interactive bonus mechanism Peter Williams
2005-12-28  6:35 ` Con Kolivas
2005-12-28  7:47   ` Nick Piggin
2005-12-29  3:51     ` Peter Williams
2005-12-29  8:02       ` Ingo Molnar [this message]
2005-12-29  8:22       ` Nick Piggin
2005-12-28  8:00 ` Ingo Molnar
2005-12-28  8:36   ` Ingo Molnar
2005-12-28 13:16     ` Peter Williams
2006-01-03  0:55     ` Peter Williams

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=20051229080206.GA22814@elte.hu \
    --to=mingo@elte.hu \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pwil3058@bigpond.net.au \
    /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