From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Michel Lespinasse <walken@google.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Greg Thelen <gthelen@google.com>, Ying Han <yinghan@google.com>
Subject: Re: [LSF/MM TOPIC] memory control groups
Date: Mon, 7 Feb 2011 10:56:08 +0530 [thread overview]
Message-ID: <20110207052608.GF27729@balbir.in.ibm.com> (raw)
In-Reply-To: <AANLkTin9EwgBRbmrDGcOKV35Z62xHb_T9Z4XPVVgxsao@mail.gmail.com>
* Michel Lespinasse <walken@google.com> [2011-02-06 07:45:05]:
> On Mon, Jan 17, 2011 at 11:14 AM, Johannes Weiner <hannes@cmpxchg.org> wrote:
> > on the MM summit, I would like to talk about the current state of
> > memory control groups, the features and extensions that are currently
> > being developed for it, and what their status is.
> >
> > I am especially interested in talking about the current runtime memory
> > overhead memcg comes with (1% of ram) and what we can do to shrink it.
> > [...]
> > Would other people be interested in discussing this?
>
> Well, YES :)
>
> In addition to what you mentioned, I believe it would be possible to
> avoid the duplication of global vs per-cgroup LRU lists. global
> scanning would translate into proportional scanning of all per-cgroup
> lists. If we could get that done, it would IMO become reasonable to
> integrate back the remaining few page_cgroup fields into struct page
> itself...
>
We thought about the duplication and proportial scanning quite a bit
prior to final design and integration, but it does not scale well as
cgroups increase in number. I would also like to discuss things
like accounting shared pages, etc.
--
Three Cheers,
Balbir
--
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>
prev parent reply other threads:[~2011-02-07 5:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 19:14 [LSF/MM TOPIC] memory control groups 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
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 [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=20110207052608.GF27729@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).