linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Michel Lespinasse <walken@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Greg Thelen <gthelen@google.com>, Ying Han <yinghan@google.com>
Subject: Re: [LSF/MM TOPIC] memory control groups
Date: Tue, 18 Jan 2011 17:45:23 +0900	[thread overview]
Message-ID: <20110118174523.5c79a032.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <AANLkTim_eDn-BS5OwmdowXMX75XgFWdcUepMJ5YBX1R7@mail.gmail.com>

On Tue, 18 Jan 2011 00:17:53 -0800
Michel Lespinasse <walken@google.com> wrote:


> > The per-memcg dirty accounting work e.g. allocates a bunch of new bits
> > in pc->flags and I'd like to hash out if this leaves enough room for
> > the structure packing I described, or whether we can come up with a
> > different way of tracking state.
> 
> This is probably longer term, but I would love to get rid of the
> duplication between global LRU and per-cgroup LRU. Global LRU could be
> approximated by scanning all per-cgroup LRU lists (in mounts
> proportional to the list lengths).
> 

I can't answer why the design, which memory cgroup's meta-page has its own LRU
rather than reusing page->lru, is selected at 1st implementation because I didn't
join the birth of memcg. Does anyone remember the reason or discussion ? 

As far as I can tell, I review patches for memcg with the viewpoint as
"Whether this patch will affect global LRU or not ? and will never break the
 algorithm of page reclaim of global LRU ?"

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 policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-01-18  8:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 19:14 Johannes Weiner
2011-01-18  1:10 ` KAMEZAWA Hiroyuki
2011-01-18  8:40   ` Johannes Weiner
2011-01-18  9:17     ` KAMEZAWA Hiroyuki
2011-01-18 10:20       ` Johannes Weiner
2011-01-19  0:14         ` KAMEZAWA Hiroyuki
2011-01-18  8:17 ` Michel Lespinasse
2011-01-18  8:45   ` KAMEZAWA Hiroyuki [this message]
2011-02-07  5:27     ` Balbir Singh
2011-01-18  8:53 ` CAI Qian
2011-01-20 10:18 ` Balbir Singh
2011-02-06 15:45 ` Michel Lespinasse
2011-02-07  5:26   ` Balbir Singh

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=20110118174523.5c79a032.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=gthelen@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=walken@google.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