OpenVZ Forum


Home » Mailing lists » Devel » Re: [PATCH v2 02/13] memcg: Kernel memory accounting infrastructure.
Re: [PATCH v2 02/13] memcg: Kernel memory accounting infrastructure. [message #45537 is a reply to message #45532] Thu, 15 March 2012 11:07 Go to previous messageGo to previous message
Glauber Costa is currently offline  Glauber Costa
Messages: 916
Registered: October 2011
Senior Member
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 =)
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [PATCH v2 06/13] slab: Add kmem_cache_gfp_flags() helper function.
Next Topic: Re: [PATCH v2 07/13] memcg: Slab accounting.
Goto Forum:
  


Current Time: Tue Sep 09 07:39:15 GMT 2025

Total time taken to generate the page: 0.06799 seconds