public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.3.1 for  2.6.16-rc5
Date: Wed, 05 Apr 2006 09:17:32 +1000	[thread overview]
Message-ID: <4432FE8C.7010900@bigpond.net.au> (raw)
In-Reply-To: <200604041627.25359.a1426z@gawab.com>

Al Boldi wrote:
> Peter Williams wrote:
>> Al Boldi wrote:
>>>>>> Control parameters for the scheduler can be read/set via files in:
>>>>>>
>>>>>> /sys/cpusched/<scheduler>/
>>> The default values for spa make it really easy to lock up the system.
>> Which one of the SPA schedulers and under what conditions?  I've been
>> mucking around with these and may have broken something.  If so I'd like
>> to fix it.
> 
> spa_no_frills, with a malloc-hog less than timeslice.  Setting 
> promotion_floor to max unlocks the console.

OK, you could also try increasing the promotion interval.

It should be noted that spa_no_frills isn't really expected to behave 
very well as it's a pure round robin scheduler.  It's intended purpose 
is as a basis for more sophisticated schedulers.  I've been thinking 
about removing it as a bootable scheduler and only making its children 
available but I find it useful to compare benchmark and other test 
results from it with that from the other schedulers to get an idea of 
the extra costs involved.

Similarly, zaphod is really just a vehicle for trying different ideas 
and the spa_ws, spa_svr and spa_ebs are the ones intended for use on 
real systems.  Of these, spa_svr isn't very good for interactive systems 
as it is designed to maximize throughput on a server (it actually beats 
spa_no_frills by about 1% on kernbench) which isn't always compatible 
with good interactive response.

Thanks,
Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

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

  reply	other threads:[~2006-04-04 23:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 11:59 [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5 Al Boldi
2006-04-03 12:13 ` Paolo Ornati
2006-04-03 23:04 ` Peter Williams
2006-04-03 23:29   ` Con Kolivas
2006-04-04  0:01     ` Peter Williams
2006-04-04  0:12       ` Con Kolivas
2006-04-04  1:29         ` Peter Williams
2006-04-04 13:27           ` Al Boldi
2006-04-04 13:27   ` Al Boldi
2006-04-04 23:17     ` Peter Williams [this message]
2006-04-05  8:16       ` Al Boldi
2006-04-05 22:53         ` Peter Williams
2006-04-07 21:32           ` Al Boldi
2006-04-08  1:29             ` Peter Williams
2006-04-08 20:31               ` Al Boldi
2006-04-09  2:58                 ` Peter Williams
2006-04-09  5:04                   ` Al Boldi
2006-04-09 23:53                     ` Peter Williams
2006-04-10 14:43                       ` Al Boldi
2006-04-11  2:07                         ` Peter Williams
2006-04-03 23:27 ` Peter Williams
2006-04-04 13:27   ` Al Boldi
2006-04-04 23:20     ` Peter Williams
2006-04-05  8:16       ` Al Boldi
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 22:32 Peter Williams
2006-03-01  2:36 ` Peter Williams
2006-04-02  2:04   ` Peter Williams
2006-04-02  6:02     ` 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=4432FE8C.7010900@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    /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