From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f197.google.com (mail-wr0-f197.google.com [209.85.128.197]) by kanga.kvack.org (Postfix) with ESMTP id B08966B0006 for ; Wed, 31 Jan 2018 15:12:21 -0500 (EST) Received: by mail-wr0-f197.google.com with SMTP id d14so11623969wre.6 for ; Wed, 31 Jan 2018 12:12:21 -0800 (PST) Received: from mail.linuxfoundation.org (mail.linuxfoundation.org. [140.211.169.12]) by mx.google.com with ESMTPS id x63si324431wme.201.2018.01.31.12.12.20 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jan 2018 12:12:20 -0800 (PST) Date: Wed, 31 Jan 2018 12:12:17 -0800 From: Andrew Morton Subject: Re: [RFC] mm/migrate: Add new migration reason MR_HUGETLB Message-Id: <20180131121217.4c80263d68a4ad4da7b170f0@linux-foundation.org> In-Reply-To: <20180131075852.GL21609@dhcp22.suse.cz> References: <20180130030714.6790-1-khandual@linux.vnet.ibm.com> <20180130075949.GN21609@dhcp22.suse.cz> <20180131075852.GL21609@dhcp22.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Anshuman Khandual , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Wed, 31 Jan 2018 08:58:52 +0100 Michal Hocko wrote: > On Wed 31-01-18 07:55:05, Anshuman Khandual wrote: > > On 01/30/2018 01:29 PM, Michal Hocko wrote: > > > On Tue 30-01-18 08:37:14, Anshuman Khandual wrote: > > >> alloc_contig_range() initiates compaction and eventual migration for > > >> the purpose of either CMA or HugeTLB allocation. At present, reason > > >> code remains the same MR_CMA for either of those cases. Lets add a > > >> new reason code which will differentiate the purpose of migration > > >> as HugeTLB allocation instead. > > > Why do we need it? > > > > The same reason why we have MR_CMA (maybe some other ones as well) at > > present, for reporting purpose through traces at the least. It just > > seemed like same reason code is being used for two different purpose > > of migration. > > But do we have any real user asking for this kind of information? It seems a reasonable cleanup: reusing MR_CMA for hugetlb just because it happens to do the right thing is a bit hacky - the two things aren't particularly related and a reader could be excused for feeling confusion. But the change seems incomplete: > + if (migratetype == MIGRATE_CMA) > + migrate_reason = MR_CMA; > + else > + migrate_reason = MR_HUGETLB; If we're going to do this cleanup then shouldn't we go all the way and add MIGRATE_HUGETLB? Alternatively... instead of adding MR_HUGETLB (and perhaps MIGRATE_HUGETLB), can we identify what characteristics these two things have in common and invent a new, more generic identifier? So that both migrate-for-CMA and migrate-for-HUGETLB will use MIGRATE_NEWNAME and MR_NEWNAME? -- 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