From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932384AbWGYCol@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932384AbWGYCol (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 24 Jul 2006 22:44:41 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932415AbWGYCol
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 24 Jul 2006 22:44:41 -0400
Received: from omta03ps.mx.bigpond.com ([144.140.82.155]:15338 "EHLO
	omta03ps.mx.bigpond.com") by vger.kernel.org with ESMTP
	id S932384AbWGYCol (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 24 Jul 2006 22:44:41 -0400
Message-ID: <44C58596.8060005@bigpond.net.au>
Date: Tue, 25 Jul 2006 12:44:38 +1000
From: Peter Williams <pwil3058@bigpond.net.au>
User-Agent: Thunderbird 1.5.0.4 (X11/20060614)
MIME-Version: 1.0
To: Al Boldi <a1426z@gawab.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2
References: <200607241857.52389.a1426z@gawab.com>
In-Reply-To: <200607241857.52389.a1426z@gawab.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authentication-Info: Submitted using SMTP AUTH PLAIN at omta03ps.mx.bigpond.com from [147.10.133.38] using ID pwil3058@bigpond.net.au at Tue, 25 Jul 2006 02:44:38 +0000
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Al Boldi wrote:
> Peter Williams wrote:
>> This version removes the hard/soft CPU rate caps from the SPA schedulers.
>>
>> A patch for 2.6.18-rc2 is available at:
>>
>> <http://prdownloads.sourceforge.net/cpuse/plugsched-6.4-for-2.6.18-rc2.pat
>> ch?download>
>>
>> Very Brief Documentation:
>>
>> You can select a default scheduler at kernel build time.  If you wish to
>> boot with a scheduler other than the default it can be selected at boot
>> time by adding:
>>
>> cpusched=<scheduler>
> 
> Any reason dynsched couldn't be merged with plugsched?

None that I know of (but I'm not familiar with dynsched).  Patches to 
add it to the mix would be accepted and once in I would try to keep it 
in step with kernel changes.

> 
>> to the boot command line where <scheduler> is one of: ingosched,
>> ingo_ll, nicksched, staircase, spa_no_frills, spa_ws, spa_svr, spa_ebs
>> or zaphod.  If you don't change the default when you build the kernel
>> the default scheduler will be ingosched (which is the normal scheduler).
>>
>> The scheduler in force on a running system can be determined by the
>> contents of:
>>
>> /proc/scheduler
> 
> It may be really great, to allow schedulers perPid parent, thus allowing the 
> stacking of different scheduler semantics.  This could aid flexibility a 
> lot.

I'm don't understand what you mean here.  Could you elaborate?

> 
> Worth a try, and should be easy to implement.
> 
>> Control parameters for the scheduler can be read/set via files in:
>>
>> /sys/cpusched/<scheduler>/
> 
> Thanks for the most important out-of-tree patch that makes 2.6 reasonable.

My pleasure,
Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce