Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756350Ab3C1HVv (ORCPT ); Thu, 28 Mar 2013 03:21:51 -0400 Received: from mx2.parallels.com ([199.115.105.18]:40133 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755848Ab3C1HVu (ORCPT ); Thu, 28 Mar 2013 03:21:50 -0400 Message-ID: <5153EFB3.5070002@parallels.com> Date: Thu, 28 Mar 2013 11:22:27 +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: Tejun Heo , Li Zefan , KAMEZAWA Hiroyuki , Johannes Weiner , , , Subject: Re: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name() References: <1364373399-17397-1-git-send-email-mhocko@suse.cz> <20130327161527.GA7395@htj.dyndns.org> <20130327161905.GN16579@dhcp22.suse.cz> <20130327162707.GO16579@dhcp22.suse.cz> In-Reply-To: <20130327162707.GO16579@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: 1523 Lines: 37 On 03/27/2013 08:27 PM, Michal Hocko wrote: > On Wed 27-03-13 09:21:02, Tejun Heo wrote: >> On Wed, Mar 27, 2013 at 9:19 AM, Michal Hocko wrote: >>>> Maybe the name could signify it's part of memcg? >>> >>> kmem_ prefix is used for all CONFIG_MEMCG_KMEM functions. I understand >>> it clashes with sl?b naming but this is out of scope of this patch IMO. >> >> Oh, it's not using kmemcg? I see. Maybe we can rename later. > > Some parts use memcg_kmem_* other kmem_. A cleanup would be nice. > Glauber? > I have been using kmem_ only in functions that will deal directly with the slab caches and with the single purpose of operating them. kmem_cache_destroy_work_func => worker interface to kmem_cache_destroy kmem_cache_destroy_memcg_children => cache destructor iterator kmem_cache_dup => interface to kmem_cache_create All the other functions start with memcg_ Analogously, all slab-side functions that deal with memcg *ends* with _memcg. except the functions that are only there to operate memcg data structures: memcg_update_all_caches. In general, those functions could very well live in the other file (slab or memcg), but they need to take locks or manipulate data structures that are internal to slab/memcg. I believe this is a sound convention. -- 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/