Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp635522imu; Fri, 16 Nov 2018 07:55:57 -0800 (PST) X-Google-Smtp-Source: AJdET5fG4cCMeptQ2GpXZPNiORdIX4UyW+q1f1I6dojJE3QcqByf9MHb3ilBm+QCF3YR2Ky0vkMk X-Received: by 2002:aa7:8552:: with SMTP id y18mr11898825pfn.83.1542383757617; Fri, 16 Nov 2018 07:55:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542383757; cv=none; d=google.com; s=arc-20160816; b=uMDasK3DM2Jwh/J12Ygrkpb4xLD9ZwfhVHL9cu6lHauWR87oHwVoY2LqOw6jrH5cVQ LLKAgveDAwxaA6c2ahNI+Xb+tPFjLqkCmS847a6GrJifhFfnubOBIuVKuXEkduECCT2n 9dDee3bn+Jl4gFiya2aV9OBeLd2R8Et9M8Lf8rRWVU3P2O1Iwplfqpu017Et13JXnj50 q5F28c5O53ZNlDAK27Ka+HYlzIa/m7wStkHhRLVukGohQTxBQRKHn5b3LV9Y+iR/LCAe yybUZarm15fepWHWfGVxYWSzcoKHWDxrMjUYDxRkJWSDXEGY8F6pmbN6j4XpbBsFZHCd STYQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6oTpeQM1rNdTtu4fW64GyJS034UbL0qBFfepliu9xrk=; b=JwV3iRz87pqXaFmyHR5dn2NBcPQJTgLUvc7vespUwnAPxTAytFNwtixnWJgfAGbjT8 Ghz6mXveYqMKVy2aDmXNueMOYUnbxtVHGv+bK3WbS3DaC9b4sIO+IYFodN9E69vacqm+ LXEs3Sda/Jg4ccUrNIRSm/GotyC+uFVvybIyndPIaPcy/6SRjzUbVTqpmHHD+DVlCU7P WIlnwoUDEbUrlNji4JZ3AYOYhvB79nP55mc5cS3TMCBq99WOnDNsOtRDeUlgbyNj3sTk cCHCOOOL4HwtzBLphKWaugfs2atc6EK0vkBEcJMBr0tOCEeSXuaAppnusjtsJMvszrNU XsUw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d3-v6si34179101plj.372.2018.11.16.07.55.42; Fri, 16 Nov 2018 07:55:57 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728684AbeKQCH7 (ORCPT + 99 others); Fri, 16 Nov 2018 21:07:59 -0500 Received: from mga02.intel.com ([134.134.136.20]:16199 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728124AbeKQCH7 (ORCPT ); Fri, 16 Nov 2018 21:07:59 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Nov 2018 07:55:05 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,240,1539673200"; d="scan'208";a="89870885" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga007.jf.intel.com with ESMTP; 16 Nov 2018 07:55:04 -0800 Date: Fri, 16 Nov 2018 08:51:41 -0700 From: Keith Busch To: Anshuman Khandual Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-mm@kvack.org, Greg Kroah-Hartman , Rafael Wysocki , Dave Hansen , Dan Williams Subject: Re: [PATCH 0/7] ACPI HMAT memory sysfs representation Message-ID: <20181116155141.GA14630@localhost.localdomain> References: <20181114224902.12082-1-keith.busch@intel.com> <1ed406b2-b85f-8e02-1df0-7c39aa21eca9@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1ed406b2-b85f-8e02-1df0-7c39aa21eca9@arm.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 16, 2018 at 11:57:58AM +0530, Anshuman Khandual wrote: > On 11/15/2018 04:19 AM, Keith Busch wrote: > > This series provides a new sysfs representation for heterogeneous > > system memory. > > > > The previous series that was specific to HMAT that this series was based > > on was last posted here: https://lkml.org/lkml/2017/12/13/968 > > > > Platforms may provide multiple types of cpu attached system memory. The > > memory ranges for each type may have different characteristics that > > applications may wish to know about when considering what node they want > > their memory allocated from. > > > > It had previously been difficult to describe these setups as memory > > rangers were generally lumped into the NUMA node of the CPUs. New > > platform attributes have been created and in use today that describe > > the more complex memory hierarchies that can be created. > > > > This series first creates new generic APIs under the kernel's node > > representation. These new APIs can be used to create links among local > > memory and compute nodes and export characteristics about the memory > > nodes. Documentation desribing the new representation are provided. > > > > Finally the series adds a kernel user for these new APIs from parsing > > the ACPI HMAT. > > Not able to see the patches from this series either on the list or on the > archive (https://lkml.org/lkml/2018/11/15/331). The send-email split the cover-letter from the series, probably something I did. Series followed immediately after: https://lkml.org/lkml/2018/11/15/332 > IIRC last time we discussed > about this and the concern which I raised was in absence of a broader NUMA > rework for multi attribute memory it might not a good idea to settle down > and freeze sysfs interface for the user space.