mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Michal Kaczmarski <fallow@op.pl>, spaminos-ker <spaminos-ker@yahoo.com>
Subject: [PATCH] V-5.0 Single Priority Array O(1) CPU Scheduler Evaluation
Date: Fri, 20 Aug 2004 12:23:39 +1000	[thread overview]
Message-ID: <412560AB.3070304@bigpond.net.au> (raw)

Version 5.0 of the various single priority array scheduler patches for
the 2.6.8.1 kernel are now available for evaluation.

This version adds NEW FEATURES to ZAPHOD and HYDRA schedulers.

1. [ZAPHOD] My proposed replacement scheduler which offers runtime
selectable choice between a priority based or entitlement based O(1)
scheduler with active/expired arrays replaced by  a single array and an
O(1) promotion mechanism plus scheduling statistics with new simplified
interactive bonus mechanism and throughput bonus mechanism.  This 
version adds hard (/proc/<TGIG>/task/<PID>/cpu_rate_hard_cap) and soft 
(/proc/<TGIG>/task/<PID>/cpu_rate_cap) CPU rate caps (in parts per 
thousand of a CPU) and an unprivileged RT mechanism (which was inspired 
by Con's SCHED_ISO patchs and will treat tasks that try to change policy 
to real time but fail due to lack of privilege as pseudo real time tasks 
and run them at MAX_RT_PRIO provided that their CPU usage rate is less 
than the threshold specified in 
/proc/sys/kernel/cpusched/unpriv_rt_threshold (in parts per thousand -- 
default 10 i.e. 1% of a CPU). Obviously setting this value to zero will 
disable the mechanism completely.). Tasks that have a soft cap of zero 
are treated much the same as Con's SCHED_BATCH tasks and will have their 
time slices multiplied by the value in 
/proc/sys/kernel/cpusched/bgnd_time_slice_multiplier (default 1):

<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8.1-spa_zaphod_FULL-v5.0?download>

2. [SC] Slightly modified version of Con Kolivas's staircase O(1)
(version 7.I) scheduler (includes SCHED_ISO and SCHED_BATCH 
modifications) with active/expired arrays replaced by a single
array and an O(1) promotion mechanism:

<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8.1-spa_hydra_FULL-v5.0?download>

3. [HYDRA] Runtime selection between staircase, priority based and
entitlement based O(1) schedulers:

<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8.1-spa_sc_FULL-v5.0?download>

Other schedulers are also available from
<https://sourceforge.net/projects/cpuse/>

Your comments and feedback are requested.

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

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


                 reply	other threads:[~2004-08-20  2:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=412560AB.3070304@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=fallow@op.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spaminos-ker@yahoo.com \
    /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

all inboxes | Powered by JetHome®