[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1336753616.14207.258.camel@gandalf.stny.rr.com>
Date: Fri, 11 May 2012 12:26:56 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Vincent Guittot <vincent.guittot@...aro.org>,
Juri Lelli <juri.lelli@...il.com>
Cc: paulmck@...ux.vnet.ibm.com, smuckle@...cinc.com, khilman@...com,
Robin.Randhawa@....com, suresh.b.siddha@...el.com,
thebigcorporation@...il.com, venki@...gle.com,
peterz@...radead.org, panto@...oniou-consulting.com, mingo@...e.hu,
paul.brett@...el.com, pdeschrijver@...dia.com, pjt@...gle.com,
efault@....de, fweisbec@...il.com, geoff@...radead.org,
tglx@...utronix.de, amit.kucheria@...aro.org,
linux-kernel@...r.kernel.org, linaro-sched-sig@...ts.linaro.org
Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP
Not really specific to HW, but Juri Lelli has been working on a deadline
scheduler. Perhaps his work may be of interest.
-- Steve
On Fri, 2012-05-11 at 18:16 +0200, Vincent Guittot wrote:
> This is a request-for-participation in a micro conference during the
> next Linux Plumber Conference (29-31st Aug).
> It'll require critical mass measured in talk submissions in the
> general area of scheduler and task management.
>
> If you're working on improving the the scheduler policy used to place
> a task on a CPU to suit your HW, we are inviting your participation
> and request you to submit a proposal to present your problem (e.g.
> power-efficiency) or a solution to solve said problem that should be
> considered by upstream developers.
>
> We've interacted with the people in To: list before in our quest to
> better understand how the scheduler works and we're hoping you all
> will consider participating in the micro-conf to help guide what kinds
> of ideas are likely to make it upstream.
>
> If you have ongoing work or ideas in the the following areas we're
> especially interested in hearing from you:
> 1. Consolidation of statistics with other frameworks (cpuidle,
> cpufreq, scheduler all seem to track their own statistics related to
> load, idleness, etc. Can this be converted to a library that is
> useable by all?)
> 2. Replacement for task consolidation on fewer CPUs aka. replacement
> for sched_mc
> 3. Improvement in the placement of activity beside tasks: timer,
> workqueue, IO, interruption
> 4. Instrumentation to calculate the compute capacity available on
> active cores and its utilization by a given workload
>
> We are thinking of organising the micro-conf as a Q & A session where
> a participant would state a problem and then there would be
> brainstorming on if this is indeed a problem and is so, how to achieve
> a solution. In other words, 20-30 minute slots of each Q & A
>
> 1. Problem statements with specific examples on why changing the
> default scheduler policy is desired
> 2. For each problem, if it is deemed not possible to accomplish easily
> today, brainstorming on what an acceptable solution would look like
> (frameworks to build upon, interfaces to use, related work in the
> area, key people to involve, etc.)
>
> Please email us if you will be attending the conference and interested
> in talking about this problem space.
>
> Regards,
> Amit & Vincent
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists