From: Con Kolivas <kernel@kolivas.org>
To: linux-kernel@vger.kernel.org,
ck kernel mailing list <ck@vds.kolivas.org>
Subject: [PATCH] Staircase scheduler v8.6
Date: Thu, 23 Sep 2004 20:36:30 +1000 [thread overview]
Message-ID: <4152A72E.8050404@kolivas.org> (raw)
Updated the staircase cpu scheduler. This version is the first in the
next development phase I've been leading it towards - removing
dependency on scheduler_tick to make it suitable for a tickless kernel.
v8.6 removes all timeslice expiration from scheduler_tick and does this
with an on-demand timer of it's own. Currently this does not offer any
major advantage over the previous version, but once more of the code is
removed from scheduler_tick and there is a mechanism for more accurate
timers not dependant on jiffies it will offer better accuracy, lower
overhead and low power advantages.
Rolled up and split patches for 2.6.9-rc2-mm2 available here:
http://ck.kolivas.org/patches/2.6/2.6.9/2.6.9-rc2-mm2/
rolled up patch:
from_2.6.9-rc2-mm2_to_staircase8.6
is a combination of:
#back-zaphod.patch
#from_2.6.9-rc2_to_staircase8.4
#s8.4_fixhotplug.diff
#s8.4-expiration_notick.diff
Cheers,
Con
P.S. I will be offline for a week as of tomorrow.
reply other threads:[~2004-09-23 10:36 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=4152A72E.8050404@kolivas.org \
--to=kernel@kolivas.org \
--cc=ck@vds.kolivas.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.