Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753480Ab2HOJVZ (ORCPT ); Wed, 15 Aug 2012 05:21:25 -0400 Received: from mx2.parallels.com ([64.131.90.16]:39030 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751463Ab2HOJVY (ORCPT ); Wed, 15 Aug 2012 05:21:24 -0400 Message-ID: <502B6956.5030508@parallels.com> Date: Wed, 15 Aug 2012 13:18:14 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 MIME-Version: 1.0 To: Greg Thelen CC: Kamezawa Hiroyuki , , , , , Michal Hocko , Johannes Weiner , Andrew Morton , Christoph Lameter , David Rientjes , Pekka Enberg , Pekka Enberg Subject: Re: [PATCH v2 06/11] memcg: kmem controller infrastructure References: <1344517279-30646-1-git-send-email-glommer@parallels.com> <1344517279-30646-7-git-send-email-glommer@parallels.com> <50254475.4000201@jp.fujitsu.com> <5028BA9E.7000302@parallels.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2497 Lines: 57 On 08/14/2012 10:58 PM, Greg Thelen wrote: > On Mon, Aug 13 2012, Glauber Costa wrote: > >>>>> + WARN_ON(mem_cgroup_is_root(memcg)); >>>>> + size = (1 << order) << PAGE_SHIFT; >>>>> + memcg_uncharge_kmem(memcg, size); >>>>> + mem_cgroup_put(memcg); >>> Why do we need ref-counting here ? kmem res_counter cannot work as >>> reference ? >> This is of course the pair of the mem_cgroup_get() you commented on >> earlier. If we need one, we need the other. If we don't need one, we >> don't need the other =) >> >> The guarantee we're trying to give here is that the memcg structure will >> stay around while there are dangling charges to kmem, that we decided >> not to move (remember: moving it for the stack is simple, for the slab >> is very complicated and ill-defined, and I believe it is better to treat >> all kmem equally here) > > By keeping memcg structures hanging around until the last referring kmem > page is uncharged do such zombie memcg each consume a css_id and thus > put pressure on the 64k css_id space? I imagine in pathological cases > this would prevent creation of new cgroups until these zombies are > dereferenced. Yes, but although this patch makes it more likely, it doesn't introduce that. If the tasks, for instance, grab a reference to the cgroup dentry in the filesystem (like their CWD, etc), they will also keep the cgroup around. > Is there any way to see how much kmem such zombie memcg are consuming? > I think we could find these with > for_each_mem_cgroup_tree(root_mem_cgroup). Yes, just need an interface for that. But I think it is something that can be addressed orthogonaly to this work, in a separate patch, not as some fundamental limitation. > Basically, I'm wanting to > know where kernel memory has been allocated. For live memcg, an admin > can cat memory.kmem.usage_in_bytes. But for zombie memcg, I'm not sure > how to get this info. It looks like the root_mem_cgroup > memory.kmem.usage_in_bytes is not hierarchically charged. > Not sure what you mean by not being hierarchically charged. It should be, when use_hierarchy = 1. As a matter of fact, I just tested it, and I do see kmem being charged all the way to the root cgroup when hierarchy is used. (we just can't limit it there) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/