From: Con Kolivas <kernel@kolivas.org>
To: linux list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, ck list <ck@vds.kolivas.org>,
Mike Galbraith <efault@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: rSDl cpu scheduler version 0.34-test patch
Date: Mon, 26 Mar 2007 11:00:21 +1000 [thread overview]
Message-ID: <200703261100.22467.kernel@kolivas.org> (raw)
This is just for testing at the moment! The reason is the size of this patch.
In the interest of evolution, I've taken the RSDL cpu scheduler and increased
the resolution of the task timekeeping to nanosecond resolution. This removes
the need for the runqueue rotation component entirely out of RSDL. The design
basically is mostly unchanged, minus over 150 lines of code for the rotation,
yet should be slightly better performing. It should be indistinguishable in
usage from v0.33.
Other changes from v0.33:
-rr interval was not being properly scaled with HZ
-fix possible race in checking task_queued in task_running_tick
-scale down rr interval for niced tasks if HZ can tolerate it
-cull list_splice_tail
What does this mean for the next version of RSDL?
Assuming all works as expected on these test patches, it will be cleanest to
submit a new series of patches for -mm with the renamed Staircase-Deadline
scheduler and new documentation (when it's done).
So for testing here are full rollups for 2.6.20.4 and 2.6.21-rc4:
http://ck.kolivas.org/patches/staircase-deadline/2.6.20.4-sd-0.34-test.patch
http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc4-sd-0.34-test.patch
The patches available also include a rollup of sched: accurate user accounting
as this code touches the same area and it is most convenient to include them
together.
(incrementals in each subdir of staircase-deadline/ for those interested).
Thanks Mike for continuing to attempt to use the cluebat on me on this one.
>From the start I wasn't sure if this was necessary or not but ends up being
less code than RSDL.
While I'm still far from being well, luckily I am in much better shape to be
able to spend the time at the pc to have done this. Thanks to all those who
expressed their concern.
--
-ck
next reply other threads:[~2007-03-26 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 1:00 Con Kolivas [this message]
2007-03-26 5:00 ` rSDl cpu scheduler version 0.34-test patch Mike Galbraith
2007-03-26 7:19 ` Con Kolivas
2007-03-26 8:10 ` Mike Galbraith
2007-03-26 8:39 ` Mike Galbraith
2007-03-26 5:46 ` Ingo Molnar
2007-03-26 5:53 ` Ingo Molnar
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=200703261100.22467.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@linux-foundation.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.