Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754753AbdGSPZP (ORCPT ); Wed, 19 Jul 2017 11:25:15 -0400 Received: from mga03.intel.com ([134.134.136.65]:40156 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751452AbdGSPZO (ORCPT ); Wed, 19 Jul 2017 11:25:14 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,381,1496127600"; d="scan'208";a="1153100511" Subject: Re: [RFC v2 0/5] surface heterogeneous memory performance information To: Bob Liu , Ross Zwisler , linux-kernel@vger.kernel.org References: <20170706215233.11329-1-ross.zwisler@linux.intel.com> 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 , 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 From: Dave Hansen Message-ID: <0e72ed92-75d0-3fe1-0ab7-ffa069d11b46@intel.com> Date: Wed, 19 Jul 2017 08:25:13 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: 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: 865 Lines: 19 On 07/19/2017 02:48 AM, Bob Liu wrote: >> Option 2: Provide the user with HMAT performance data directly in >> sysfs, allowing applications to directly access it without the need >> for the library and daemon. >> > Is it possible to do the memory allocation automatically by the > kernel and transparent to users? It sounds like unreasonable that > most users should aware this detail memory topology. It's possible, but I'm not sure this is something we automatically want to see added to the kernel. I look at it like NUMA. We have lots of details available about how things are connected. But, "most users" are totally unaware of this. We give them decent default policies and the ones that need more can do so with the NUMA APIs. These patches provide the framework to help users/apps who *do* care and want to make intelligent, topology-aware decisions.