linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lespinasse <walken@google.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	lsf@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Lsf] [LSF][MM] rough agenda for memcg.
Date: Thu, 31 Mar 2011 20:18:04 -0700	[thread overview]
Message-ID: <BANLkTimb+GeeiSPnX23Wfo-=1mHzNiJ=FQ@mail.gmail.com> (raw)
In-Reply-To: <20110331155931.GG12265@random.random>

On Thu, Mar 31, 2011 at 8:59 AM, Andrea Arcangeli <aarcange@redhat.com> wrote:
> Hi KAMEZAWA,
>
> On Thu, Mar 31, 2011 at 11:01:13AM +0900, KAMEZAWA Hiroyuki wrote:
>> 1. Memory cgroup : Where next ? 1hour (Balbir Singh/Kamezawa)
>
> Originally it was 30min and then there was a topic "Working set
> estimation" for another 30 min. That has been converted to "what's
> next continued", so I assume that you can add the Working set
> estimation as a subtopic.

I see this session on the second day of the agenda. I think I'd like
to keep it a separate session; however I probably don't need the full
30 minutes; I should be able to give out the extra time to the virtual
machine memory sizing discussion that is slotted afterwards.

>> 2. Memcg Dirty Limit and writeback 30min(Greg Thelen)
>> 3. Memcg LRU management 30min (Ying Han, Michal Hocko)
>> 4. Page cgroup on a diet (Johannes Weiner)
>> 2.5 hours. This seems long...or short ? ;)
>
> Overall we've been seeing plenty of memcg emails, so I guess 2.5 hours
> are ok. And I wouldn't say we're not in the short side.

I am happy to see many parties interested in discussing memcg. I don't
think 2.5 hours are too much either.

One issue I would like to hear about is the way memcg is kept well
separated from the rest of the VM - as seen by the fact that only one
C file knows about the insides of struct mem_cgroup, that memcg has
been careful not to modify global reclaim, etc... I think this was
necessary early on when few people were interested in memcg, but now
that every major linux shop works on it it seems to me there is no
justification for that strong separation anymore. I'd like to see that
addressed explicitly because the concensus on that will affect what we
can do about memcg LRU management, page cgroup diet and a few other
topics.

>>   IV) Diet of page_cgroup (for 30-min)
>>       Maybe this can be combined with III.
>
> Looks a good plan to me, but others are more directly involved in
> memcg than me so feel free to decide! About the diet topic it was
> suggested by Johannes so I'll let him comment on it if he wants.

If the diet is successful enough, I think we could even consider
merging struct page_cgroup into struct page.

-- 
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.

--
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>

  parent reply	other threads:[~2011-04-01  3:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  2:01 [LSF][MM] rough agenda for memcg KAMEZAWA Hiroyuki
2011-03-31  5:52 ` Greg Thelen
2011-03-31 12:27   ` [Lsf] " Jan Kara
2011-03-31  6:01 ` Balbir Singh
2011-03-31  6:03 ` Ying Han
2011-03-31  9:15 ` Zhu Yanhai
2011-04-01  2:36   ` Michel Lespinasse
2011-03-31  9:23 ` [Lsf] " Pavel Emelyanov
2011-03-31 16:20   ` Andrea Arcangeli
2011-03-31 18:14     ` Ying Han
2011-03-31 19:00       ` Pavel Emelyanov
2011-03-31 19:16         ` Ying Han
2011-03-31 19:22           ` Ying Han
2011-03-31 15:59 ` Andrea Arcangeli
2011-03-31 20:06   ` Johannes Weiner
2011-04-01  3:18   ` Michel Lespinasse [this message]
2011-04-01  1:16 ` KAMEZAWA Hiroyuki

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='BANLkTimb+GeeiSPnX23Wfo-=1mHzNiJ=FQ@mail.gmail.com' \
    --to=walken@google.com \
    --cc=aarcange@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).