From: Con Kolivas <kernel@kolivas.org>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Schedulers benchmark - Was: [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6
Date: Thu, 18 Aug 2005 07:35:03 +1000 [thread overview]
Message-ID: <200508180735.04162.kernel@kolivas.org> (raw)
In-Reply-To: <6bffcb0e0508171104311942ff@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Thu, 18 Aug 2005 04:04, Michal Piotrowski wrote:
> Hi,
> here are additional staircase scheduler benchmarks.
>
> (make all -j8)
>
> scheduler:
> staircase
>
> sched_compute=1
> real 49m48.619s
> user 77m20.788s
> sys 6m7.653s
Very nice thank you.
Since you are benchmarking, here is an unofficial update to the staircase
patch to the current non-plugsched version which will affect the results of
interbench (it won't change the benchmark results of compute mode).
Cheers,
Con
[-- Attachment #2: staircase_update.patch --]
[-- Type: text/x-diff, Size: 751 bytes --]
Index: linux-2.6.13-rc6-plugsched/kernel/staircase.c
===================================================================
--- linux-2.6.13-rc6-plugsched.orig/kernel/staircase.c 2005-08-18 07:32:34.000000000 +1000
+++ linux-2.6.13-rc6-plugsched/kernel/staircase.c 2005-08-18 07:33:10.000000000 +1000
@@ -64,8 +64,8 @@ int sched_compute = 0;
*compute setting is reserved for dedicated computational scheduling
*and has ten times larger intervals.
*/
-#define _RR_INTERVAL ((10 * HZ / 1000) ? : 1)
-#define RR_INTERVAL() (_RR_INTERVAL * (1 + 9 * sched_compute))
+#define _RR_INTERVAL ((5 * HZ / 1000) ? : 1)
+#define RR_INTERVAL() (_RR_INTERVAL * (1 + 19 * sched_compute))
#define TASK_PREEMPTS_CURR(p, rq) \
((p)->prio < (rq)->curr->prio)
next prev parent reply other threads:[~2005-08-17 21:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 4:46 [ANNOUNCE][RFC] PlugSched-5.2.4 for 2.6.12 and 2.6.13-rc6 Peter Williams
2005-08-15 12:29 ` Michal Piotrowski
[not found] ` <43012427.9080406@bigpond.net.au>
[not found] ` <4301330B.3070400@bigpond.net.au>
2005-08-16 12:54 ` Michal Piotrowski
2005-08-17 8:00 ` Con Kolivas
2005-08-17 11:23 ` Michal Piotrowski
2005-08-17 12:31 ` Con Kolivas
2005-08-16 21:49 ` Schedulers benchmark - Was: " Michal Piotrowski
2005-08-17 8:10 ` Peter Williams
2005-08-17 9:03 ` Con Kolivas
2005-08-17 18:04 ` Michal Piotrowski
2005-08-17 21:35 ` Con Kolivas [this message]
2005-08-17 23:15 ` Peter Williams
2005-08-17 23:16 ` Con Kolivas
2005-08-17 23:48 ` Peter Williams
2005-08-17 23:45 ` Con Kolivas
2005-08-19 3:09 ` Michal Piotrowski
2005-08-19 3:28 ` Lee Revell
2005-08-19 3:41 ` Con Kolivas
2005-08-19 4:41 ` Peter Williams
2005-08-19 4:36 ` Con Kolivas
2005-08-19 20:13 ` Lee Revell
2005-08-20 0:31 ` Con Kolivas
2005-08-20 3:04 ` Lee Revell
2005-08-20 18:52 ` Lee Revell
2005-08-19 4:26 ` Peter Williams
2005-08-17 11:59 ` Michal Piotrowski
2005-08-21 1:34 ` Michal Piotrowski
2005-08-21 1:47 ` Con Kolivas
2005-08-21 4:16 ` Michal Piotrowski
2005-08-21 4:22 ` Con Kolivas
2005-08-21 4:44 ` Michal Piotrowski
2005-08-21 4:49 ` Con Kolivas
2005-08-21 1:37 ` Michal Piotrowski
[not found] ` <4309125B.4020707@bigpond.net.au>
2005-08-22 11:39 ` Michal Piotrowski
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=200508180735.04162.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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