From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f197.google.com (mail-pf0-f197.google.com [209.85.192.197]) by kanga.kvack.org (Postfix) with ESMTP id 4DC606B0279 for ; Fri, 7 Jul 2017 01:30:49 -0400 (EDT) Received: by mail-pf0-f197.google.com with SMTP id d62so23139133pfb.13 for ; Thu, 06 Jul 2017 22:30:49 -0700 (PDT) Received: from hqemgate16.nvidia.com (hqemgate16.nvidia.com. [216.228.121.65]) by mx.google.com with ESMTPS id 6si1692232plc.131.2017.07.06.22.30.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Jul 2017 22:30:48 -0700 (PDT) Subject: Re: [RFC v2 0/5] surface heterogeneous memory performance information References: <20170706215233.11329-1-ross.zwisler@linux.intel.com> From: John Hubbard Message-ID: <7cb3b9c4-9082-97e9-ebfd-542243bf652b@nvidia.com> Date: Thu, 6 Jul 2017 22:30:46 -0700 MIME-Version: 1.0 In-Reply-To: <20170706215233.11329-1-ross.zwisler@linux.intel.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Ross Zwisler , linux-kernel@vger.kernel.org Cc: "Anaczkowski, Lukasz" , "Box, David E" , "Kogut, Jaroslaw" , "Lahtinen, Joonas" , "Moore, Robert" , "Nachimuthu, Murugasamy" , "Odzioba, Lukasz" , "Rafael J. Wysocki" , "Rafael J. Wysocki" , "Schmauss, Erik" , "Verma, Vishal L" , "Zheng, Lv" , Andrew Morton , Dan Williams , Dave Hansen , Greg Kroah-Hartman , Jerome Glisse , Len Brown , Tim Chen , devel@acpica.org, linux-acpi@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org On 07/06/2017 02:52 PM, Ross Zwisler wrote: [...] > > The naming collision between Jerome's "Heterogeneous Memory Management > (HMM)" and this "Heterogeneous Memory (HMEM)" series is unfortunate, but I > was trying to stick with the word "Heterogeneous" because of the naming of > the ACPI 6.2 Heterogeneous Memory Attribute Table table. Suggestions for > better naming are welcome. > Hi Ross, Say, most of the places (file names, function and variable names, and even print statements) where this patchset uses hmem or HMEM, it really seems to mean, the Heterogeneous Memory Attribute Table. That's not *always* true, but given that it's a pretty severe naming conflict, how about just changing: hmem --> hmat HMEM --> HMAT ...everywhere? Then you still have Heterogeneous Memory in the name, but there is enough lexical distance (is that a thing? haha) between HMM and HMAT to keep us all sane. :) With or without the above suggestion, there are a few places (Kconfig, comments, prints) where we can more easily make it clear that HMM != HMEM (or HMAT), so for those I can just comment on them separately in the individual patches. thanks, john h -- 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