From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
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>,
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: Re: Scheduler BOF @ LinuxCon.EU/ELCE
Date: Mon, 17 Oct 2011 13:45:06 -0400 [thread overview]
Message-ID: <1318873506.4722.3.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1318872925.4172.81.camel@twins>
On Mon, 2011-10-17 at 19:35 +0200, Peter Zijlstra wrote:
> 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?
>
I would recommend that LinuxCon is the best place for this. We could
decide on a good bar to hold it perhaps, after we've been there for a
week to figure out what bar would be good for this :)
It should be after KS so we can get a good idea of what Paul has to say
about scheduler load tracking.
IIUC, LinuxCon has a way to add new BoF sessions at the conference. It
may be best to wait till then, and just tell people that ask you, to
look for it on the LinuxCon schedule postings.
-- Steve
next prev parent reply other threads:[~2011-10-17 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 17:35 Peter Zijlstra
2011-10-17 17:45 ` Steven Rostedt [this message]
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=1318873506.4722.3.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.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=peterz@infradead.org \
--cc=pjt@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®