Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932372Ab3CVKCx (ORCPT ); Fri, 22 Mar 2013 06:02:53 -0400 Received: from mx2.parallels.com ([199.115.105.18]:46817 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752473Ab3CVKCv (ORCPT ); Fri, 22 Mar 2013 06:02:51 -0400 Message-ID: <514C2C72.5090402@parallels.com> Date: Fri, 22 Mar 2013 14:03:30 +0400 From: Glauber Costa User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Michal Hocko CC: Li Zefan , Tejun Heo , LKML , Cgroups , , KAMEZAWA Hiroyuki , Johannes Weiner Subject: Re: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name() References: <514A60CD.60208@huawei.com> <20130321090849.GF6094@dhcp22.suse.cz> <20130321102257.GH6094@dhcp22.suse.cz> <514BB23E.70908@huawei.com> <20130322080749.GB31457@dhcp22.suse.cz> <514C1388.6090909@huawei.com> <514C14BF.3050009@parallels.com> <20130322093141.GE31457@dhcp22.suse.cz> <514C2754.4080701@parallels.com> <20130322094832.GG31457@dhcp22.suse.cz> In-Reply-To: <20130322094832.GG31457@dhcp22.suse.cz> 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: 1794 Lines: 54 On 03/22/2013 01:48 PM, Michal Hocko wrote: > On Fri 22-03-13 13:41:40, Glauber Costa wrote: >> On 03/22/2013 01:31 PM, Michal Hocko wrote: >>> On Fri 22-03-13 12:22:23, Glauber Costa wrote: >>>> On 03/22/2013 12:17 PM, Li Zefan wrote: >>>>>> GFP_TEMPORARY groups short lived allocations but the mem cache is not >>>>>>> an ideal candidate of this type of allocations.. >>>>>>> >>>>> I'm not sure I'm following you... >>>>> >>>>> char *memcg_cache_name() >>>>> { >>>>> char *name = alloc(); >>>>> return name; >>>>> } >>>>> >>>>> kmem_cache_dup() >>>>> { >>>>> name = memcg_cache_name(); >>>>> kmem_cache_create_memcg(name); >>>>> free(name); >>>>> } >>>>> >>>>> Isn't this a short lived allocation? >>>>> >>>> >>>> Hi, >>>> >>>> Thanks for identifying and fixing this. >>>> >>>> Li is right. The cache name will live long, but this is because the >>>> slab/slub caches will strdup it internally. So the actual memcg >>>> allocation is short lived. >>> >>> OK, I have totally missed that. Sorry about the confusion. Then all the >>> churn around the allocation is pointless, no? >>> What about: >> >> If we're really not concerned about stack, then yes. Even if always >> running from workqueues, a PAGE_SIZEd stack variable seems risky to me. > > This is not on stack. It is static > Ah, right, I totally missed that. And then you're taking the mutex. But actually, you don't need to take the mutex. All calls to kmem_cache_dup are protected by the memcg_cache_mutex. So you should be able to just use the buffer without further problems. -- 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/