From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Suleiman Souhlal <suleiman@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Pavel Emelyanov <xemul@openvz.org>, Ying Han <yinghan@google.com>,
linux-mm@kvack.org
Subject: Re: memcg: slab control
Date: Mon, 30 Nov 2009 14:47:00 +0530 [thread overview]
Message-ID: <20091130091700.GK2970@balbir.in.ibm.com> (raw)
In-Reply-To: <d26f1ae00911260213t3e389ccfqa03d18c459210b2e@mail.gmail.com>
* Suleiman Souhlal <suleiman@google.com> [2009-11-26 02:13:17]:
> On 11/26/09, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > I think it is easier to write a slab controller IMHO.
>
> One potential problem I can think of with writing a slab controller
> would be that the user would have to estimate what fraction of the
> amount of memory slab should be allowed to use, which might not be
> ideal.
>
> If you wanted to limit a cgroup to a total of 1GB of memory, you might
> not care if the job wants to use 0.9 GB of user memory and 0.1GB of
> slab or if it wants to use 0.9GB of slab and 0.1GB of user memory..
>
Hmm.. true, yes not caring about how memory usage is partitioned is
nice (we have memsw for very similar reasons).
> Because of this, it might be more practical to integrate the slab
> accounting in memcg.
>
I tend to agree, but I would like to see the early design and
thoughts. Like Kame pointed, integrating their accounting can be an
issue.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-30 9:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 23:08 David Rientjes
2009-11-26 1:14 ` KAMEZAWA Hiroyuki
2009-11-26 8:50 ` Balbir Singh
2009-11-26 8:56 ` KAMEZAWA Hiroyuki
2009-11-26 9:10 ` Pavel Emelyanov
2009-11-26 9:33 ` KAMEZAWA Hiroyuki
2009-11-26 9:56 ` Pavel Emelyanov
2009-11-26 10:24 ` Suleiman Souhlal
2009-11-26 12:31 ` Pavel Emelyanov
2009-11-26 12:52 ` Suleiman Souhlal
2009-12-01 7:40 ` Balbir Singh
2009-11-27 7:15 ` Ying Han
2009-11-27 9:45 ` Pavel Emelyanov
2009-12-01 5:14 ` KOSAKI Motohiro
2009-11-30 22:57 ` David Rientjes
2009-12-01 10:31 ` Pavel Emelyanov
2009-12-01 22:29 ` David Rientjes
2009-12-01 7:36 ` Balbir Singh
2009-12-01 10:40 ` Pavel Emelyanov
2009-12-01 15:14 ` Balbir Singh
2009-12-02 10:14 ` Pavel Emelyanov
2009-12-02 10:19 ` Balbir Singh
2009-12-02 10:51 ` Pavel Emelyanov
2009-11-30 22:55 ` David Rientjes
2009-12-01 10:39 ` Pavel Emelyanov
2009-11-26 10:13 ` Suleiman Souhlal
2009-11-30 9:17 ` Balbir Singh [this message]
2009-11-30 22:45 ` David Rientjes
2009-11-26 1:17 ` KAMEZAWA Hiroyuki
2009-11-26 10:01 ` Suleiman Souhlal
2009-11-26 2:35 ` KOSAKI Motohiro
2009-11-27 7:01 ` Ying Han
2009-11-27 9:48 ` Pavel Emelyanov
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=20091130091700.GK2970@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=suleiman@google.com \
--cc=xemul@openvz.org \
--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