LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Vaidyanathan Srinivasan <email@example.com>
To: Ranjit Manomohan <firstname.lastname@example.org>
Cc: email@example.com, Mike Galbraith <firstname.lastname@example.org>,
Nikhil Rao <email@example.com>, Salman Qazi <firstname.lastname@example.org>,
Dhaval Giani <email@example.com>,
Peter Zijlstra <firstname.lastname@example.org>,
Ingo Molnar <email@example.com>,
Thomas Gleixner <firstname.lastname@example.org>,
Venkatesh Pallipadi <email@example.com>,
Paul Turner <firstname.lastname@example.org>
Subject: Re: [ANNOUNCE] Linsched for 2.6.35 released
Date: Tue, 19 Oct 2010 10:22:56 +0530 [thread overview]
Message-ID: <20101019045256.GA20232@dirshya.in.ibm.com> (raw)
* Ranjit Manomohan <email@example.com> [2010-10-12 10:29:54]:
> I would like to announce the availability of the Linux Scheduler Simulator
> (Linsched) for 2.6.35.
> Originally developed at the University of North Carolina, LinSched is a
> user-space program that hosts the Linux scheduling subsystem.
> Its purpose is to provide a tool for observing and modifying the behavior
> of the Linux scheduler. This makes it a valuable tool in prototyping new
> Linux scheduling policies in a way that may be easier (or otherwise
> less painful or time-consuming) to many developers when compared
> to working with real hardware.
The idea and framework looks very interesting. I tried it out in
order to understand the workload model and verification model and it
worked fine for the test cases that you have provided.
> Since Linsched allows arbitrary hardware topologies to be modeled,
> it enables testing of scheduler changes on hardware that may not be
> easily accessible to the developer. For example, most developers don't
> have access to a quad-core quad-socket box, but they can use LinSched
> to see how their changes affect the scheduler on such boxes.
I am interested in trying this simulator in order to
design/study/verify task placement logic within the SMP loadbalancer.
Basically the effects of SD_POWERSAVINGS_BALANCE, SD_PREFER_SIBLING,
etc in various topologies.
The current interface and verification mechanism is to create tasks
and observe the runtime received by each task. In an ideal
loadbalancer situation, all tasks should have received runtime
proportional to their priority.
Can you help me figure out how to get to kstat_cpu() or per-cpu
kernel_stat accounting/utilisation metrics within the simulation?
Thanks for sharing the framework.
next prev parent reply other threads:[~2010-10-19 4:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 17:29 Ranjit Manomohan
2010-10-19 4:52 ` Vaidyanathan Srinivasan [this message]
2010-11-16 1:52 ` Ranjit Manomohan
2011-02-08 18:10 ` Vaidyanathan Srinivasan
2011-02-15 18:25 ` Ranjit Manomohan
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [ANNOUNCE] Linsched for 2.6.35 released' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).