All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Mike Galbraith <efault@gmx.de>, Paul Turner <pjt@google.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	rostedt <rostedt@goodmis.org>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Venkatesh Pallipadi <venki@google.com>,
	Glauber Costa <glommer@parallels.com>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Scheduler BOF @ LinuxCon.EU/ELCE
Date: Mon, 17 Oct 2011 19:35:25 +0200	[thread overview]
Message-ID: <1318872925.4172.81.camel@twins> (raw)

Hi,

several people have expressed interest of talking to me about the
scheduler during the RTLWS/KS/LinuxCon.EU time-frame. Since I've just
about lost track of who all wanted to talk about what and who can and
can not make it out to Prague I need help ;-)

Also, since I'm too dis-organized (and mostly busy) to really arrange
something, can someone volunteer to arrange a BOF or cafe with beer to
discuss things?

The topics I'm most interested in are:

 - power optimized load-balancing;
    do packing based on cpu utilization 
    fix the current interface of sched_{mc,ht}_power_savings

 - integration of the cpufreq/idle governors and the scheduler
    use the idle guestimate for NO_HZ
    use $foo for $prev-topic to reduce double accounting etc.

 - what can we do about the cgroup crap and how can we win some
   of the performance back;
    start with fixing the cgroup enabled but unused case
    continue from there..

    pjt was rewriting load tracking, do tell us about it
        also tell us what the status of ncrao's hackery is,
        or does your hackery replace that?

Things I specifically do not want to talk about:

 - systemd, its shit, go away.

             reply	other threads:[~2011-10-17 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 17:35 Peter Zijlstra [this message]
2011-10-17 17:45 ` Scheduler BOF @ LinuxCon.EU/ELCE Steven Rostedt
2011-10-18  7:14 ` Vincent Guittot
2011-10-18  9:16 ` Paul Turner
2011-10-18  9:25   ` Peter Zijlstra
2011-10-18  9:36 ` Glauber Costa
2011-10-18  9:56   ` selva vinayakam

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=1318872925.4172.81.camel@twins \
    --to=peterz@infradead.org \
    --cc=arjan@linux.intel.com \
    --cc=efault@gmx.de \
    --cc=glommer@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=pjt@google.com \
    --cc=rostedt@goodmis.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=vatsa@in.ibm.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.