Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759445Ab2EKSoo (ORCPT ); Fri, 11 May 2012 14:44:44 -0400 Received: from mx2.parallels.com ([64.131.90.16]:32776 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759075Ab2EKSom (ORCPT ); Fri, 11 May 2012 14:44:42 -0400 Message-ID: <4FAD5DA2.70803@parallels.com> Date: Fri, 11 May 2012 15:42:42 -0300 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Christoph Lameter CC: , , , , Tejun Heo , Li Zefan , Greg Thelen , Suleiman Souhlal , Michal Hocko , Johannes Weiner , , Pekka Enberg Subject: Re: [PATCH v2 04/29] slub: always get the cache from its page in kfree References: <1336758272-24284-1-git-send-email-glommer@parallels.com> <1336758272-24284-5-git-send-email-glommer@parallels.com> <4FAD531D.6030007@parallels.com> <4FAD566C.3000804@parallels.com> <4FAD585A.4070007@parallels.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [187.105.248.83] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1786 Lines: 42 On 05/11/2012 03:32 PM, Christoph Lameter wrote: > On Fri, 11 May 2012, Glauber Costa wrote: > >> Thank you in advance for your time reviewing this! > > Where do I find the rationale for all of this? Trouble is that pages can > contain multiple objects f.e. so accounting of pages to groups is a bit fuzzy. > I have not followed memcg too much since it is not relevant (actual > it is potentially significantly harmful given the performance > impact) to the work loads that I am using. > It's been spread during last discussions. The user-visible part is documented in the last patch, but I'll try to use this space here to summarize more of the internals (it can also go somewhere in the tree if needed): We want to limit the amount of kernel memory tasks inside a memory cgroup use. slab is not the only one of them, but it is quite significant. For that, the least invasive, and most reasonable way we found to do it, is to create a copy of each slab inside the memcg. Or almost: we lazy create them, so only slabs that are touched by the memcg are created. So we don't mix pages from multiple memcgs in the same cache - we believe that would be too confusing. /proc/slabinfo reflects this information, by listing the memcg-specific slabs. This also appears in a memcg-specific memory.kmem.slabinfo. Also note that accounting is not done until kernel memory is limited. And if no memcg is limited, the code is wrapped inside static_key branches. So it should be completely patched out if you don't put stuff inside memcg. -- 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/