All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@gmail.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	paulmck@linux.vnet.ibm.com, smuckle@quicinc.com, khilman@ti.com,
	Robin.Randhawa@arm.com, suresh.b.siddha@intel.com,
	thebigcorporation@gmail.com, venki@google.com,
	peterz@infradead.org, panto@antoniou-consulting.com,
	mingo@elte.hu, paul.brett@intel.com, pdeschrijver@nvidia.com,
	pjt@google.com, efault@gmx.de, fweisbec@gmail.com,
	geoff@infradead.org, tglx@linutronix.de,
	amit.kucheria@linaro.org, linux-kernel@vger.kernel.org,
	linaro-sched-sig@lists.linaro.org
Subject: Re: Plumbers: Tweaking scheduler policy micro-conf RFP
Date: Tue, 15 May 2012 10:41:43 +0200	[thread overview]
Message-ID: <4FB216C7.6020604@gmail.com> (raw)
In-Reply-To: <CAKfTPtA8EJeYVfpYTF7sh44ANOCUzE_eLkmYgE+bg25Vsgoj1Q@mail.gmail.com>

On 05/11/2012 06:38 PM, Vincent Guittot wrote:
> On 11 May 2012 18:26, Steven Rostedt<rostedt@goodmis.org>  wrote:
>> Not really specific to HW, but Juri Lelli has been working on a deadline
>> scheduler. Perhaps his work may be of interest.
>
> Yes for sure, if Juri is agree to present his work
>

Sure! It will be really interesting for me.
I'm setting up the proposal. I'll send it today.

Thanks and Regards,

- Juri
  
> Vincent
>>
>> -- 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
>>
>>

  reply	other threads:[~2012-05-15  8:41 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 16:16 Plumbers: Tweaking scheduler policy micro-conf RFP Vincent Guittot
2012-05-11 16:26 ` Steven Rostedt
2012-05-11 16:38   ` Vincent Guittot
2012-05-15  8:41     ` Juri Lelli [this message]
2012-05-15  0:53 ` Paul E. McKenney
2012-05-15  8:02 ` Vincent Guittot
2012-05-15  8:34   ` mou Chen
2012-05-15  9:07     ` Vincent Guittot
2012-05-15  9:17       ` Pantelis Antoniou
2012-05-15 10:28         ` Peter Zijlstra
2012-05-15 11:35           ` Pantelis Antoniou
2012-05-15 11:58             ` Peter Zijlstra
2012-05-15 12:32               ` Pantelis Antoniou
2012-05-15 12:59                 ` Peter Zijlstra
2012-05-19 14:58               ` Luming Yu
2012-05-15 20:26             ` valdis.kletnieks
2012-05-15 20:33               ` Peter Zijlstra
2012-05-16 12:08               ` Pantelis Antoniou
2012-05-15 12:23   ` Peter Zijlstra
2012-05-15 12:27     ` Peter Zijlstra
2012-05-15 12:57     ` Vincent Guittot
2012-05-15 13:00       ` Peter Zijlstra
2012-05-15 15:05         ` Vincent Guittot
2012-05-15 15:19           ` Paul E. McKenney
2012-05-15 15:27             ` Vincent Guittot
2012-05-15 15:35           ` Peter Zijlstra
2012-05-15 15:45             ` Peter Zijlstra
2012-05-16 18:30             ` Peter Zijlstra
2012-05-19 17:08               ` Linus Torvalds
2012-05-19 22:55                 ` Peter Zijlstra
2012-05-22  2:38                   ` Chen
2012-05-22  5:14                     ` Chen
2012-05-30  7:20                       ` Ingo Molnar
2012-05-23 15:03                     ` Ingo Molnar
2012-05-23 15:43                       ` Joe Perches
2012-05-23 15:50                         ` Ingo Molnar
2012-05-23 15:56                           ` Joe Perches
2012-05-23 15:59                             ` Ingo Molnar
2012-05-29 18:17                           ` [PATCH] printk: Shrink printk_sched buffer size, eliminate it when !CONFIG_PRINTK Joe Perches
2012-06-05 16:04                             ` Joe Perches
2012-06-06  7:25                               ` Ingo Molnar
2012-06-06  7:33                             ` Ingo Molnar
2012-06-06  7:42                               ` Joe Perches
2012-05-19 23:13                 ` Plumbers: Tweaking scheduler policy micro-conf RFP Peter Zijlstra
2012-05-19 23:22                 ` Peter Zijlstra
2012-05-21  7:16                   ` Ingo Molnar
2012-05-21 16:56                     ` Linus Torvalds
2012-05-16 18:49             ` Vaidyanathan Srinivasan
2012-05-16 19:40               ` Peter Zijlstra
2012-05-16 21:20             ` Vincent Guittot
     [not found]             ` <20120518161817.GE18312@e103034-lin.cambridge.arm.com>
2012-05-18 16:24               ` Morten Rasmussen
2012-05-18 16:39                 ` Peter Zijlstra
2012-05-18 16:46                 ` Pantelis Antoniou
2012-05-15 16:30           ` Vaidyanathan Srinivasan
2012-05-15 18:13             ` Vincent Guittot

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=4FB216C7.6020604@gmail.com \
    --to=juri.lelli@gmail.com \
    --cc=Robin.Randhawa@arm.com \
    --cc=amit.kucheria@linaro.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=geoff@infradead.org \
    --cc=khilman@ti.com \
    --cc=linaro-sched-sig@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=panto@antoniou-consulting.com \
    --cc=paul.brett@intel.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pdeschrijver@nvidia.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=rostedt@goodmis.org \
    --cc=smuckle@quicinc.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=thebigcorporation@gmail.com \
    --cc=venki@google.com \
    --cc=vincent.guittot@linaro.org \
    /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.