Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751747AbbEFOrF (ORCPT ); Wed, 6 May 2015 10:47:05 -0400 Received: from cantor2.suse.de ([195.135.220.15]:41748 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750826AbbEFOrD (ORCPT ); Wed, 6 May 2015 10:47:03 -0400 Date: Wed, 6 May 2015 16:46:59 +0200 From: Michal Hocko To: Vladimir Davydov Cc: Andrew Morton , Johannes Weiner , Tejun Heo , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Greg Thelen , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] gfp: add __GFP_NOACCOUNT Message-ID: <20150506144659.GO14550@dhcp22.suse.cz> References: <20150506115941.GH14550@dhcp22.suse.cz> <20150506122431.GA29387@esperanza> <20150506123541.GK14550@dhcp22.suse.cz> <20150506132510.GB29387@esperanza> <20150506135520.GN14550@dhcp22.suse.cz> <20150506142951.GC29387@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150506142951.GC29387@esperanza> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 830 Lines: 20 On Wed 06-05-15 17:29:51, Vladimir Davydov wrote: [...] > My point is that MEMCG is the only subsystem of the kernel that tries to > do full memory accounting, and there is no point in introducing another > one, because we already have it. Then I really do not get why the gfp flag cannot be specific about that. Anyway, it doesn't really make much sense to bikeshed about the flag here. So if both you and Johannes agree on the name I will not stand in the way. I will go and check into include/linux/gfp.h anytime I will try to remember the flag name... -- Michal Hocko SUSE Labs -- 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/