From: "Stephan Bärwolf" <stephan.baerwolf@tu-ilmenau.de>
To: linux-kernel@vger.kernel.org
Cc: linaro-kernel@lists.linaro.org, panto@antoniou-consulting.com
Subject: Re: [RFC] Scheduler recorder and playback
Date: Thu, 08 Mar 2012 16:20:05 +0100 [thread overview]
Message-ID: <4F58CE25.5070906@tu-ilmenau.de> (raw)
In-Reply-To: <85A3EFC3-FAE0-4B3A-AAA0-85FA435A9F7B@antoniou-consulting.com>
Hi Pantelis,
what is your primary goal?
Saving power? Improving interactivity? Be more cache-optimal?
I think recording the scheduling (without drastically slowing it down) is hard to do,
since it ticks at least HZ times per second.
Replay such an recording (on a differeny platform) seems even harder to me.
Since different cpus (and number of them), different speed and a very likely not
reproduceable process-setup may noise completely the replay.
Do you also want to record/replay the behaviour of the more important loadbalancer, too?
Did you thought to compare different platforms by simply having syntetically generated
loads? (I.e. see interbench -> http://users.on.net/~ckolivas/interbench/)
If you are interested in examing the scheduling-behaviour as a function of the tuneables
(and even the HZ) - and if you are interested in getting better latency, maybe you
are interested in nitro-patch for the scheduler?
(I currently don't have an external patch-file, but you can get it integrated from
https://github.com/baerwolf/linux-stephan/commits/v3.2.9-stephan-201203030000 )
Nitro enables you to do so some things, like:
* tune the scheduler at configuration point
* increase the ticker-frequency way above 1000Hz
* tune the ticker-freq. from userspace during runtime
* change the scheduling-algo for idle-tasks
regards Stephan
next prev parent reply other threads:[~2012-03-08 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 13:20 [RFC] Scheduler recorder and playback Pantelis Antoniou
2012-03-08 15:20 ` Stephan Bärwolf [this message]
2012-03-08 15:46 ` Pantelis Antoniou
2012-03-08 15:45 ` Frederic Weisbecker
2012-03-08 16:21 ` Pantelis Antoniou
2012-03-08 17:40 ` Yadwinder Singh Brar
2012-03-08 17:57 ` Pantelis Antoniou
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=4F58CE25.5070906@tu-ilmenau.de \
--to=stephan.baerwolf@tu-ilmenau.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=panto@antoniou-consulting.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