All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Andi Kleen <ak@linux.intel.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Paul Turner <pjt@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
	Rik van Riel <riel@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Samy Al Bahra <sbahra@repnop.org>
Subject: Re: Plumbers 2015 -- Performance and Scalability track
Date: Fri, 1 May 2015 13:07:54 +0000 (UTC)	[thread overview]
Message-ID: <475112629.41788.1430485674040.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1430407494.2011.33.camel@stgolabs.net>

----- Original Message -----
> Hello,
> 
> I am hoping we can have a scaling track this year. The purpose of this
> email is to 1) confirm some of the key participants, 2) suggestions for
> other key participants and 3) more topics so that we can have a big
> enough pool to screen correctly for what's really worth discussing.
> 
> I have setup the wiki page here with some initial tentative topics Paul
> and I came up with:
> 
> http://wiki.linuxplumbersconf.org/2015:performance_and_scalability
> 
> They are obviously specific to things that interest us. As such, if you
> would like to attend and/or have specific topics that would like
> discussed, please update the wiki.
> 
> The goals for this track are several: 1) get to know general
> experimental work going on (kernel and userland). 2) learn about real
> bottlenecks/issues people are running into, and 3) present wip topics
> that improve performance and need some face to face discussion. As
> mentioned in the wiki, this track should only cover performance topics
> that are not specific to other tracks

Hi!

I'm interested to participate. My only constraint is that the tracing
summit is on August 20th, and overlaps with one day of LPC. Let's hope
we can find a way to have this track on a different day.

I'm planning to work some more on a efficient per-cpu spinlock & data
prototype for userspace. This could be an interesting topic for LPC.
I'm aware of Paul Turner's work in this area. Let's say I'm trying a
less intrusive approach.

Thanks!

Mathieu

> 
> Thanks,
> Davidlohr
> 
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2015-05-01 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 15:24 Plumbers 2015 -- Performance and Scalability track Davidlohr Bueso
2015-05-01 13:07 ` Mathieu Desnoyers [this message]
2015-05-01 15:16   ` Paul E. McKenney
2015-06-04 16:35 ` Davidlohr Bueso

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=475112629.41788.1430485674040.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=ak@linux.intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dave@stgolabs.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=raghavendra.kt@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=sbahra@repnop.org \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    /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.