From: Ying Han <yinghan@google.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Hugh Dickins <hughd@google.com>,
Glauber Costa <glommer@parallels.com>,
Kir Kolyshkin <kir@parallels.com>,
Pavel Emelianov <xemul@parallels.com>,
GregThelen <gthelen@google.com>, Paul Turner <pjt@google.com>,
Tim Hockin <thockin@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>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: Proposed memcg meeting at October Kernel Summit/European LinuxCon in Prague
Date: Thu, 13 Oct 2011 13:54:55 -0700 [thread overview]
Message-ID: <CALWz4iwOA3AgSDoiVSHBGc81SLNBPu=yy2GF1hwU_9xDhvpfSg@mail.gmail.com> (raw)
In-Reply-To: <1318428864.3027.10.camel@dabdike.int.hansenpartnership.com>
On Wed, Oct 12, 2011 at 7:14 AM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Mon, 2011-10-10 at 19:35 -0700, Ying Han wrote:
>> On Thu, Sep 29, 2011 at 2:30 PM, Hugh Dickins <hughd@google.com> wrote:
>> > On Thu, Sep 29, 2011 at 4:54 AM, Michal Hocko <mhocko@suse.cz> wrote:
>> >> On Tue 27-09-11 13:16:19, James Bottomley wrote:
>> >> > On Mon, 2011-09-26 at 15:10 +0200, Michal Hocko wrote:
>> >> > > On Thu 22-09-11 12:16:47, James Bottomley wrote:
>> >> > > > Hi All,
>> >> > >
>> >> > > Hi,
>> >> > >
>> >> > > >
>> >> > > > 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.
>> >> > >
>> >> > > I am not going to be at KS but I am in Prague. I would be happy to meet
>> >> > > as well if it is possible.
>> >> >
>> >> > Certainly.
>> >>
>> >> OK, then add me as well.
>> >
>> > Please include Ying Han and Hugh Dickins; but regrettably, scheduling
>> > issues will prevent Greg Thelen from attending.
>>
>> Thank you Hugh. I will be in KS as well as the memcg meeting. Sorry
>> for the late reply due to OOO in the past few weeks.
>>
>> James,
>>
>> Thank you so much for organizing this and please keep us informed when
>> the detailed schedule is out :)
>
> We're a bit blocked on this. We have some proposals, particularly in
> the area of shrinkers, but we know you have patches in this area which
> we haven't seen ... can you post the google memgc patches just for
> reference (they don't have to be final, or even highly polished) just so
> we have a common base to work from?
sorry for getting back late.
We are preparing the patches and should be able to send out before the
summit. The patchset itself does the kernel slab accounting in memcg,
and something we would like to discuss in the memcg meeting in
Wednesday as well.
Thanks
--Ying
>
> James
>
>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-13 20:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 12:16 Proposed memcg meeting at October Kernel Summit/European LinuxCon in Prague James Bottomley
2011-09-22 15:06 ` 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 [this message]
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='CALWz4iwOA3AgSDoiVSHBGc81SLNBPu=yy2GF1hwU_9xDhvpfSg@mail.gmail.com' \
--to=yinghan@google.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave@linux.vnet.ibm.com \
--cc=glommer@parallels.com \
--cc=gthelen@google.com \
--cc=hughd@google.com \
--cc=jweiner@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kir@parallels.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=paul@paulmenage.org \
--cc=pjt@google.com \
--cc=thockin@google.com \
--cc=xemul@parallels.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).