From: Glauber Costa <glommer@parallels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, Suleiman Souhlal <suleiman@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [RFC] simple system for enable/disable slabs being tracked by memcg.
Date: Thu, 29 Mar 2012 13:51:50 +0200 [thread overview]
Message-ID: <4F744CD6.2080809@parallels.com> (raw)
In-Reply-To: <4F73A6E8.8010402@jp.fujitsu.com>
On 03/29/2012 02:03 AM, KAMEZAWA Hiroyuki wrote:
> Hmm, but having private format of list is good ?
> In another idea, how about having 3 files as device cgroup ?
>
> memory.kmem.slabs.allow (similar to device.allow)
> memory.kmem.slabs.deny (similar to device.deny)
> memory.kmem.slabs.list (similar to device.list)
>
I forgot to comment on this point.
I fear #files explosion, but since one the drawbacks of our beloved cgroups
IMHO is the sheer inconsistency among them (which we're trying to fix), if
there is precedence for that, we can use it. Certainly solves the problem.
--
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:[~2012-03-29 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 16:42 [RFC] simple system for enable/disable slabs being tracked by memcg Glauber Costa
2012-03-29 0:01 ` Suleiman Souhlal
2012-03-29 11:10 ` Glauber Costa
2012-03-29 0:03 ` KAMEZAWA Hiroyuki
2012-03-29 11:22 ` Glauber Costa
2012-03-29 11:51 ` Glauber Costa [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=4F744CD6.2080809@parallels.com \
--to=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=suleiman@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).