linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <jbottomley@parallels.com>
To: Glauber Costa <glommer@parallels.com>,
	Kir Kolyshkin <kir@parallels.com>,
	Pavel Emelianov <xemul@parallels.com>,
	GregThelen <gthelen@google.com>,
	"pjt@google.com" <pjt@google.com>,
	Tim Hockin <thockin@google.com>, Ying Han <yinghan@google.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Johannes Weiner <jweiner@redhat.com>,
	Dave Hansen <dave@linux.vnet.ibm.com>,
	Paul Menage <paul@paulmenage.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Proposed memcg meeting at October Kernel Summit/European LinuxCon in Prague
Date: Thu, 22 Sep 2011 12:16:47 +0000	[thread overview]
Message-ID: <1316693805.10571.25.camel@dabdike> (raw)

Hi All,

One of the major work items that came out of the Plumbers conference
containers and Cgroups meeting was the need to work on memcg:

http://www.linuxplumbersconf.org/2011/ocw/events/LPC2011MC/tracks/105

(see etherpad and presentations)

Since almost everyone will be either at KS or LinuxCon, I thought doing
a small meeting on the Wednesday of Linux Con (so those at KS who might
not be staying for the whole of LinuxCon could attend) might be a good
idea.  The object would be to get all the major players to agree on
who's doing what.  You can see Parallels' direction from the patches
Glauber has been posting.  Google should shortly be starting work on
other aspects of the memgc as well.

As a precursor to the meeting (and actually a requirement to make it
effective) we need to start posting our preliminary patches and design
ideas to the mm list (hint, Google people, this means you).

I think I've got all of the interested parties in the To: field, but I'm
sending this to the mm list just in case I missed anyone.  If everyone's
OK with the idea (and enough people are going to be there) I'll get the
Linux Foundation to find us a room.

James


             reply	other threads:[~2011-09-22 12:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 12:16 James Bottomley [this message]
2011-09-22 15:06 ` Proposed memcg meeting at October Kernel Summit/European LinuxCon in Prague Balbir Singh
2011-09-22 15:43   ` James Bottomley
2011-09-22 23:12     ` Balbir Singh
2011-09-22 15:59 ` Tim Hockin
2011-09-26  2:23 ` KAMEZAWA Hiroyuki
2011-09-26 13:10 ` Michal Hocko
2011-09-27 18:16   ` James Bottomley
2011-09-29 11:54     ` Michal Hocko
2011-09-29 21:30       ` Hugh Dickins
2011-09-29 23:32         ` Paul Turner
2011-10-11  2:35         ` Ying Han
2011-10-12 14:14           ` James Bottomley
2011-10-13 20:54             ` Ying Han
2011-10-13 20:58               ` James Bottomley
2011-10-13 22:13                 ` Ying Han
2011-10-14  7:44                   ` Glauber Costa
2011-09-27 18:48 ` Johannes Weiner
2011-10-23 16:12 ` James Bottomley
2011-10-26  9:36   ` James Bottomley

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=1316693805.10571.25.camel@dabdike \
    --to=jbottomley@parallels.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=glommer@parallels.com \
    --cc=gthelen@google.com \
    --cc=jweiner@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kir@parallels.com \
    --cc=linux-mm@kvack.org \
    --cc=paul@paulmenage.org \
    --cc=pjt@google.com \
    --cc=thockin@google.com \
    --cc=xemul@parallels.com \
    --cc=yinghan@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).