public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
	kernel@kolivas.org, solt2@dns.toxicfilms.tv,
	linux-kernel@vger.kernel.org
Subject: Re: Trying out SCHED_BATCH
Date: Thu, 30 Dec 2004 11:16:03 -0500	[thread overview]
Message-ID: <41D429C3.8010805@tmr.com> (raw)
In-Reply-To: <20041229232028.055f8786.akpm@osdl.org>

Andrew Morton wrote:
> Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:
> 
>>Andrew, 
>> what's your plan for the staircase scheduler ?
> 
> 
> I have none, frankly.  I haven't seen any complaints about the current
> scheduler.
> 
> If someone can identify bad behaviour in the current scheduler which
> staircase improves then please describe a tescase which the scheduler
> developers can use to reproduce the situation.

Of course that may result in just another band-aid on the current 
scheduler rather than a change.
> 
> If, after that, we deem that the problem cannot be feasibly fixed within the
> context of the current scheduler and that the problem is sufficiently
> serious to justify wholesale replacement of the scheduler then sure,
> staircase is an option.

More to the point, was there a problem with plugable schedulers? It 
would be both technically and politically better to let people try, use, 
and write schedulers for special case loads, just as we have for io 
scheduling.

I didn't find staircase to be the solution to any of my problems, but it 
would be nice to let all the people who are improving schedulers have an 
easy way to try new ideas (easier than building a whole new kernel, that 
is).

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-12-30 16:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25 11:31 Trying out SCHED_BATCH Rajsekar
2004-12-25 11:41 ` Con Kolivas
2004-12-29 20:14   ` Maciej Soltysiak
2004-12-29 20:28     ` Con Kolivas
2004-12-29 22:46       ` Paolo Ciarrocchi
2004-12-29 22:56         ` Con Kolivas
2004-12-30  7:12           ` Paolo Ciarrocchi
2004-12-30  7:20             ` Andrew Morton
2004-12-30  7:36               ` Paolo Ciarrocchi
2004-12-30  7:41                 ` Con Kolivas
2004-12-30 16:16               ` Bill Davidsen [this message]
2005-01-02  0:26                 ` Peter Williams
2004-12-25 11:46 ` Matan Peled
2004-12-25 18:45 ` Bill Davidsen
2004-12-25 23:09   ` 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=41D429C3.8010805@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.com \
    --cc=solt2@dns.toxicfilms.tv \
    /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