Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756473AbdLTVQz (ORCPT ); Wed, 20 Dec 2017 16:16:55 -0500 Received: from bombadil.infradead.org ([65.50.211.133]:46187 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755637AbdLTVQw (ORCPT ); Wed, 20 Dec 2017 16:16:52 -0500 Date: Wed, 20 Dec 2017 13:16:49 -0800 From: Matthew Wilcox To: Dave Hansen Cc: Ross Zwisler , Michal Hocko , linux-kernel@vger.kernel.org, "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, linux-api@vger.kernel.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT Message-ID: <20171220211649.GA32200@bombadil.infradead.org> References: <20171214021019.13579-1-ross.zwisler@linux.intel.com> <20171214130032.GK16951@dhcp22.suse.cz> <20171218203547.GA2366@linux.intel.com> <20171220181937.GB12236@bombadil.infradead.org> <2da89d31-27a3-34ab-2dbb-92403c8215ec@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2da89d31-27a3-34ab-2dbb-92403c8215ec@intel.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1264 Lines: 23 On Wed, Dec 20, 2017 at 12:22:21PM -0800, Dave Hansen wrote: > On 12/20/2017 10:19 AM, Matthew Wilcox wrote: > > I don't know what the right interface is, but my laptop has a set of > > /sys/devices/system/memory/memoryN/ directories. Perhaps this is the > > right place to expose write_bw (etc). > > Those directories are already too redundant and wasteful. I think we'd > really rather not add to them. In addition, it's technically possible > to have a memory section span NUMA nodes and have different performance > properties, which make it impossible to represent there. > > In any case, ACPI PXM's (Proximity Domains) are guaranteed to have > uniform performance properties in the HMAT, and we just so happen to > always create one NUMA node per PXM. So, NUMA nodes really are a good fit. I think you're missing my larger point which is that I don't think this should be exposed to userspace as an ACPI feature. Because if you do, then it'll also be exposed to userspace as an openfirmware feature. And sooner or later a devicetree feature. And then writing a portable program becomes an exercise in suffering. So, what's the right place in sysfs that isn't tied to ACPI? A new directory or set of directories under /sys/devices/system/memory/ ?