From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx139.postini.com [74.125.245.139]) by kanga.kvack.org (Postfix) with SMTP id 199626B005D for ; Wed, 15 Aug 2012 14:11:51 -0400 (EDT) Received: by ggnf4 with SMTP id f4so2544475ggn.14 for ; Wed, 15 Aug 2012 11:11:50 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <000001392aec1926-72b3a631-1fb1-460c-803d-38c4405151e1-000000@email.amazonses.com> References: <1344517279-30646-1-git-send-email-glommer@parallels.com> <1344517279-30646-5-git-send-email-glommer@parallels.com> <20120814162144.GC6905@dhcp22.suse.cz> <502B6D03.1080804@parallels.com> <20120815123931.GF23985@dhcp22.suse.cz> <000001392ac15404-43a3fd2c-a6d3-4985-b173-74bb586ad47c-000000@email.amazonses.com> <502BBC35.809@parallels.com> <000001392aec1926-72b3a631-1fb1-460c-803d-38c4405151e1-000000@email.amazonses.com> Date: Wed, 15 Aug 2012 11:11:49 -0700 Message-ID: Subject: Re: [PATCH v2 04/11] kmem accounting basic infrastructure From: Ying Han Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter Cc: Glauber Costa , Michal Hocko , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, devel@openvz.org, Johannes Weiner , Andrew Morton , kamezawa.hiroyu@jp.fujitsu.com, David Rientjes , Pekka Enberg On Wed, Aug 15, 2012 at 8:34 AM, Christoph Lameter wrote: > On Wed, 15 Aug 2012, Glauber Costa wrote: > >> On 08/15/2012 06:47 PM, Christoph Lameter wrote: >> > On Wed, 15 Aug 2012, Michal Hocko wrote: >> > >> >>> That is not what the kernel does, in general. We assume that if he wants >> >>> that memory and we can serve it, we should. Also, not all kernel memory >> >>> is unreclaimable. We can shrink the slabs, for instance. Ying Han >> >>> claims she has patches for that already... >> >> >> >> Are those patches somewhere around? >> > >> > You can already shrink the reclaimable slabs (dentries / inodes) via >> > calls to the subsystem specific shrinkers. Did Ying Han do anything to >> > go beyond that? >> > >> That is not enough for us. >> We would like to make sure that the objects being discarded belong to >> the memcg which is under pressure. We don't need to be perfect here, and >> an occasional slip is totally fine. But if in general, shrinking from >> memcg A will mostly wipe out objects from memcg B, we harmed the system >> in return for nothing good. > > How can you figure out which objects belong to which memcg? The ownerships > of dentries and inodes is a dubious concept already. I figured it out based on the kernel slab accounting. obj->page->kmem_cache->memcg --Ying > > -- > 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/ . > Don't email: email@kvack.org -- 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/ . Don't email: email@kvack.org