linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: paulmck@kernel.org, liam.howlett@oracle.com, willy@infradead.org,
	michel@lespinasse.org, andrealmeid@collabora.com,
	peterz@infradead.org, alex.kogan@oracle.com, longman@redhat.com,
	tglx@linutronix.de, tim.c.chen@intel.com,
	anthony.yznaga@oracle.com
Subject: LPC 2021: Plumbers Performance and Scalability track
Date: Wed, 16 Jun 2021 10:59:35 -0700	[thread overview]
Message-ID: <20210616175935.pnnkjrtzywasmdso@offworld> (raw)

Hello,

This year the Performance and Scalability track for Plumbers is back and with this email,
we are hoping 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.

Here is a first very loose list of ideas, which are obviously specific to things that
interest us.

https://www.linuxplumbersconf.org/event/11/page/104-accepted-microconferences#cont-perform

As such, if you would like to attend and/or have specific topics that would like discussed,
please do submit it at (ensuring selecting the Performance and Scalability MC):

https://www.linuxplumbersconf.org/event/11/abstracts/#submit-abstract

With performance and scalability being a bit generic terms, this track should only cover
related topics that are not specific to other tracks.

Thank you.

On behalf of Daniel, Pavel and myself.


                 reply	other threads:[~2021-06-16 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210616175935.pnnkjrtzywasmdso@offworld \
    --to=dave@stgolabs.net \
    --cc=alex.kogan@oracle.com \
    --cc=andrealmeid@collabora.com \
    --cc=anthony.yznaga@oracle.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=michel@lespinasse.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@intel.com \
    --cc=willy@infradead.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