From: Peter Williams <pwil3058@bigpond.net.au>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Michal Kaczmarski <fallow@op.pl>
Subject: [PATCH] V-3.0 Single Priority Array O(1) CPU Scheduler Evaluation
Date: Sat, 07 Aug 2004 11:44:57 +1000 [thread overview]
Message-ID: <41143419.6000407@bigpond.net.au> (raw)
Version 3.1 of the various single priority array scheduler patches for
2.6.7, 2.6.8-rc2 and 2.6.8-rc3 kernels are now available for evaluation.
This is a bug fix release to fix a problem caused by sched_clock() not
being monotonic. This meant that when measuring small time intervals by
taking the difference between successive calls to sched_clock() there is
a possibility of obtaining a negative value (or, as unsigned long longs
are being used, a very big one). One unfortunate consequence of this is
that adding to non zero intervals together could lead to a zero result
and possible divide by zero problems.
1. [ZAPHOD] 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 interactive bonus mechanism and throughput bonus
mechanism:
2.6.7
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.7-spa_zaphod_FULL-v3.1?download>
2.6.8-rc2
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc2-spa_zaphod_FULL-v3.1?download>
2.6.8-rc3
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc3-spa_zaphod_FULL-v3.1?download>
2. Slightly modified version of Con Kolivas's staircase O(1) scheduler
with active/expired arrays replaced by a single array and an O(1)
promotion mechanism:
2.6.7
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.7-spa_sc_FULL-v3.1?download>
2.6.8-rc2
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc2-spa_sc_FULL-v3.1?download>
2.6.8-rc3
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc3-spa_sc_FULL-v3.1?download>
3. [HYDRA] Runtime selection between staircase, priority based and
entitlement based O(1) schedulers:
2.6.7
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.7-spa_hydra_FULL-v3.1?download>
2.6.8-rc2
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc2-spa_hydra_FULL-v3.1?download>
2.6.8-rc3
<http://prdownloads.sourceforge.net/cpuse/patch-2.6.8-rc3-spa_hydra_FULL-v3.1?download>
Other schedulers are also available from
<https://sourceforge.net/projects/cpuse/>
So as not to interfere with the staircase scheduler's evaluation I do
not propose to release patches for rc3-mm kernels unless requested.
I'm in the process of simplifying my schedulers (I got carried away with
the theory) in order to reduce their overhead and hope to release a new
slimmer version early next week. Also on the "to do" list are CPU rate
caps.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next reply other threads:[~2004-08-07 1:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 1:44 Peter Williams [this message]
[not found] <2oEEn-197-9@gated-at.bofh.it>
2004-08-02 13:27 ` [PATCH] V-3.0 Single Priority Array O(1) CPU Scheduler Evaluation Andi Kleen
2004-08-03 0:27 ` Peter Williams
2004-08-03 3:53 ` Andrew Morton
2004-08-03 4:38 ` Peter Williams
2004-08-03 6:51 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 6:31 Peter Williams
2004-08-02 13:42 ` William Lee Irwin III
2004-08-03 0:33 ` Peter Williams
2004-08-03 2:03 ` William Lee Irwin III
2004-08-03 3:39 ` Peter Williams
2004-08-03 10:49 ` William Lee Irwin III
2004-08-04 0:37 ` Peter Williams
2004-08-04 0:50 ` William Lee Irwin III
2004-08-04 1:36 ` Peter Williams
2004-08-04 1:51 ` William Lee Irwin III
2004-08-04 2:40 ` Peter Williams
2004-08-04 7:05 ` Ingo Molnar
2004-08-04 7:44 ` William Lee Irwin III
2004-08-05 1:06 ` Peter Williams
2004-08-05 2:00 ` William Lee Irwin III
2004-08-05 2:12 ` 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=41143419.6000407@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=fallow@op.pl \
--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