linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: lsf@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Lsf] [LSF][MM] rough agenda for memcg.
Date: Fri, 1 Apr 2011 10:16:13 +0900	[thread overview]
Message-ID: <20110401101613.de0e79dc.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20110331110113.a01f7b8b.kamezawa.hiroyu@jp.fujitsu.com>

On Thu, 31 Mar 2011 11:01:13 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:

> So, for this slot, I'd like to discuss
> 
>   I) Softlimit/Isolation (was 3-A) for 1hour
>      If we have extra time, kernel memory accounting or file-cache handling
>      will be good.
>    
>   II) Dirty page handling. (for 30min)
>      Maybe we'll discuss about per-memcg inode queueing issue.
> 
>   III) Discussing the current and future design of LRU.(for 30+min)
> 
>   IV) Diet of page_cgroup (for 30-min)
>       Maybe this can be combined with III.
> 

Thank you for feedbacks. I think I don't have enough time to reply all..
So, I'm sorry I make a reply in this style.

Hearing your replies and other private feedbacks, I think following schedule
will be good. And I want to spend time for topics for which patches are
posted and someone measured the cost and benefits.

1) How memcg users uses it and what's wanted ?  (for 1st session/30min)

   At start, we should sort out what's wanted as functions of memcg.
   We need to hear use cases. And see what is the problem, now. 
   Maybe we can discuss requirements for kernel memory limit, here.
   (I think we have no time to discuss implemenation in official slot.)

2) What's next ? : 30min.
   At first, Pavel will explain what OpenVZ does.
   Then, we can discuss about softlimit/isolation and LRU design.
   I think it will be a hot topic in the next half year with dirty page handling.
   
3) Dirty Page Handling.

4) Discussing LRU, costs and fairness.
   At first, need to discuss effect of per-memcg background reclaim.
   Then, discuss about new LRU design including removing page_cgroup->lru.
 
5) Diet of page_cgroup and others.
   I don't think diet topic requires full 30min. So, some extra topic is....
   It seems some guys want to overcommit vmem size with cgroup.


A topic from me was adding a memcg only-for-file-cache...but I have no patches.
Postphone until I have a concrete idea and patches.

Thanks,
-Kame






--
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  1:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31  2:01 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
2011-04-01  1:16 ` KAMEZAWA Hiroyuki [this message]

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=20110401101613.de0e79dc.kamezawa.hiroyu@jp.fujitsu.com \
    --to=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