public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'Mike Galbraith'" <efault@gmx.de>,
	"'akpm@osdl.org'" <akpm@osdl.org>,
	"'rml@tech9.net'" <rml@tech9.net>,
	"'Ingo Molnar'" <mingo@elte.hu>,
	"'Con Kolivas'" <kernel@kolivas.org>,
	"'Elladan'" <elladan@eskimo.com>,
	"'Chris Siebenmann'" <cks@utcc.utoronto.ca>
Subject: Re: Maximum frequency of re-scheduling (minimum time quantum	) que stio n
Date: Fri, 09 Jul 2004 11:46:29 +1000	[thread overview]
Message-ID: <40EDF8F5.2060808@yahoo.com.au> (raw)
In-Reply-To: <40EDD980.4040608@bigpond.net.au>

Peter Williams wrote:
> Povolotsky, Alexander wrote:
> 
>> Hi Peter,
>>
>>
>>> By freeing "time slice"s from their involvement in active/expired 
>>> priority array switching etc., the various single priority array 
>>> schedulers (e.g. Con Kolivas's staircase scheduler and my SPA "pb" 
>>> and "eb" schedulers) that are under development raise the possibility 
>>> of allowing the time slice for SCHED_RR tasks to be different to that 
>>> of ordinary tasks or even for it to be set separately for each 
>>> SCHED_RR task.  Whether this is desirable or not is another question.
>>
>>
>>
>> IMHO (I am new in Linux),- if this functionality could be either 
>> optionally
>> configured at compile time or be optionally invokable at run time (or
>> combination of both) - why not to have it ? - this addition enhances 
>> choices
>> of scheduling,
>> which is good.
>>
>> Is there a chance such functionality will make into Linux 2.6 as a 
>> patch (at
>> some later time) ?
> 
> 
> Not until the current scheduler is replaced with a single priority array 
> scheduler.  However, if there's enough interest, I could add this 
> functionality to the CPU scheduler evaluation patch so that people could 
> experiment with it (BUT it would be at the bottom of my to do list).

You are mistaken. The current scheduler only uses a single array
for realtime tasks. Functionality would be trivial to implement
now.

> 
>>
>> By the way - what is the "mechanism" of decision making process (among 
>> Linux
>> kernel developers) on such things ?
> 
> 
> I'll leave this question to someone more knowledgeable.
> 

I'd defer a final decision to others more knowlegeable of course
(Ingo, Andrew, Linus?), however it would be almost out of the
question to do a wholesale replacement in 2.6.

However well tested your scheduler might be, it needs several
orders of magnitude more testing ;) Maybe the best we can hope
for is compile time selectable alternatives.

  parent reply	other threads:[~2004-07-09  1:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 13:01 Re: Maximum frequency of re-scheduling (minimum time quantum ) que stio n Povolotsky, Alexander
2004-07-08 23:32 ` Peter Williams
2004-07-08 23:41   ` William Lee Irwin III
2004-07-09  1:46   ` Nick Piggin [this message]
2004-07-09  1:57     ` Andrew Morton
2004-07-09  4:18       ` Con Kolivas
2004-07-09  4:48         ` Andrew Morton
2004-07-09  3:04     ` Peter Williams
     [not found] <320586863@toto.iv>
2004-07-13  0:20 ` peterc
  -- strict thread matches above, loose matches on Subject: below --
2004-07-07  9:48 Maximum frequency of re-scheduling (minimum time quantum) " Povolotsky, Alexander
2004-07-07 15:52 ` Elladan
2004-07-07  7:59 Povolotsky, Alexander
2004-07-07  8:30 ` Bernd Eckenfels
2004-07-07  8:59 ` Elladan
2004-07-07 10:26   ` Con Kolivas
     [not found] <313680C9A886D511A06000204840E1CF08F42FD4@whq-msgusr-02.pit .comms.marconi.com>
2004-07-05 15:33 ` Mike Galbraith
2004-07-05 14:18 Povolotsky, Alexander
2004-07-05 23:26 ` 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=40EDF8F5.2060808@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Alexander.Povolotsky@marconi.com \
    --cc=akpm@osdl.org \
    --cc=cks@utcc.utoronto.ca \
    --cc=efault@gmx.de \
    --cc=elladan@eskimo.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pwil3058@bigpond.net.au \
    --cc=rml@tech9.net \
    /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