Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933175Ab2EKSWN (ORCPT ); Fri, 11 May 2012 14:22:13 -0400 Received: from mx2.parallels.com ([64.131.90.16]:58347 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932215Ab2EKSWJ (ORCPT ); Fri, 11 May 2012 14:22:09 -0400 Message-ID: <4FAD585A.4070007@parallels.com> Date: Fri, 11 May 2012 15:20:10 -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> 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: 1541 Lines: 40 On 05/11/2012 03:17 PM, Christoph Lameter wrote: > On Fri, 11 May 2012, Glauber Costa wrote: > >> On 05/11/2012 03:06 PM, Christoph Lameter wrote: >>> On Fri, 11 May 2012, Glauber Costa wrote: >>> >>>>> Adding a VM_BUG_ON may be useful to make sure that kmem_cache_free is >>>>> always passed the correct slab cache. >>>> >>>> Well, problem is , it isn't always passed the "correct" slab cache. >>>> At least not after this series, since we'll have child caches associated >>>> with >>>> the main cache. >>>> >>>> So we'll pass, for instance, kmem_cache_free(dentry_cache...), but will in >>>> fact free from the memcg copy of the dentry cache. >>> >>> Urg. But then please only do this for the MEMCG case and add a fat big >>> warning in kmem_cache_free. >> >> I can do that, of course. >> Another option if you don't oppose, is to add another field in the kmem_cache >> structure (I tried to keep them at a minimum), >> to record the parent cache we got created from. >> >> Then, it gets trivial to do the following: >> >> VM_BUG_ON(page->slab != s&& page->slab != s->parent_cache); > > Sounds ok but I need to catch up on what this whole memcg thing in slab > allocators should accomplish in order to say something definite. > Fair enough. Thank you in advance for your time reviewing this! -- 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/