[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F61CD63.4090007@parallels.com>
Date: Thu, 15 Mar 2012 15:07:15 +0400
From: Glauber Costa <glommer@...allels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
CC: Suleiman Souhlal <ssouhlal@...eBSD.org>, <cgroups@...r.kernel.org>,
<suleiman@...gle.com>, <penberg@...nel.org>, <cl@...ux.com>,
<yinghan@...gle.com>, <hughd@...gle.com>, <gthelen@...gle.com>,
<peterz@...radead.org>, <dan.magenheimer@...cle.com>,
<hannes@...xchg.org>, <mgorman@...e.de>,
<James.Bottomley@...senPartnership.com>, <linux-mm@...ck.org>,
<devel@...nvz.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 02/13] memcg: Kernel memory accounting infrastructure.
On 03/15/2012 04:48 AM, KAMEZAWA Hiroyuki wrote:
>>> - What happens when a new cgroup created ?
>> >
>> > mem_cgroup_create() is called =)
>> > Heh, jokes apart, I don't really follow here. What exactly do you mean?
>> > There shouldn't be anything extremely out of the ordinary.
>> >
>
> Sorry, too short words.
>
> Assume a cgroup with
> cgroup.memory.limit_in_bytes=1G
> cgroup.memory.kmem.limit_in_bytes=400M
>
> When a child cgroup is created, what should be the default values.
> 'unlimited' as current implementation ?
> Hmm..maybe yes.
I think so, yes. I see no reason to come up with any default values
in memcg. Yes, your allocations can fail due to your parent limits.
But since I never heard of any machine with
9223372036854775807 bytes of memory, that is true even for the root memcg =)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists