Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756565AbdLVROE (ORCPT ); Fri, 22 Dec 2017 12:14:04 -0500 Received: from mga14.intel.com ([192.55.52.115]:24754 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756079AbdLVROB (ORCPT ); Fri, 22 Dec 2017 12:14:01 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,441,1508828400"; d="scan'208";a="4912450" Subject: Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT To: Anshuman Khandual , Ross Zwisler , linux-kernel@vger.kernel.org References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <2d6420f7-0a95-adfe-7390-a2aea4385ab2@linux.vnet.ibm.com> Cc: "Anaczkowski, Lukasz" , "Box, David E" , "Kogut, Jaroslaw" , "Koss, Marcin" , "Koziej, Artur" , "Lahtinen, Joonas" , "Moore, Robert" , "Nachimuthu, Murugasamy" , "Odzioba, Lukasz" , "Rafael J. Wysocki" , "Rafael J. Wysocki" , "Schmauss, Erik" , "Verma, Vishal L" , "Zheng, Lv" , Andrew Morton , Balbir Singh , Brice Goglin , Dan Williams , Jerome Glisse , John Hubbard , Len Brown , Tim Chen , devel@acpica.org, linux-acpi@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org From: Dave Hansen Message-ID: <5d7df981-69c2-e371-f48d-13c418fff134@intel.com> Date: Fri, 22 Dec 2017 09:13:59 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <2d6420f7-0a95-adfe-7390-a2aea4385ab2@linux.vnet.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 833 Lines: 15 On 12/21/2017 07:09 PM, Anshuman Khandual wrote: > I had presented a proposal for NUMA redesign in the Plumbers Conference this > year where various memory devices with different kind of memory attributes > can be represented in the kernel and be used explicitly from the user space. > Here is the link to the proposal if you feel interested. The proposal is > very intrusive and also I dont have a RFC for it yet for discussion here. I think that's the best reason to "re-use NUMA" for this: it's _not_ intrusive. Also, from an x86 perspective, these HMAT systems *will* be out there. Old versions of Linux *will* see different types of memory as separate NUMA nodes. So, if we are going to do something different, it's going to be interesting to un-teach those systems about using the NUMA APIs for this. That ship has sailed.