Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2061083imu; Thu, 17 Jan 2019 07:47:16 -0800 (PST) X-Google-Smtp-Source: ALg8bN6od0DOgU/553/+rcHGBJ5IqvQA2Hkh5W28cMGLhuUtY2J/q40cNNBnTVhCMxM4erOOwkkF X-Received: by 2002:a17:902:128c:: with SMTP id g12mr14886344pla.146.1547740036251; Thu, 17 Jan 2019 07:47:16 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547740036; cv=none; d=google.com; s=arc-20160816; b=hrW7mk0wPeekjPXPaBqIvTu0r0u4VH1L9o95mnNrV2C/V5aZfg+qoePW7NaVY3/9on UPiBmvpBUThBpFogMrC8MWcXcnOsQh2S/0zwqlZBkwhJSDoPsm9ipBpawq2/9VPW62sf HM3aTxSBjpBwF0AqYH1KLw4qv13TtdOTXUam2PcXDCZJd5r7HhqlEDYql+XO9eAuiNN5 VmGCSfRAFiHLozA8wGPPF7OYhIJZKGJ9GNMY+KywW4BKn1UqoOIzy5flWkKP+6I8QuBN OL3MrFefo53M1SKSE66FaOcZLzrqH/cfAcvqK39FAlge8Ees1NhWwqKYNvy6tp2mER58 CTCA== 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=wajzeNTldyHV0w9z1WD3eE5jLrp4BI3UMAI2TgIV1g4=; b=VXxOEtwhKRxVuqSn7oBGuqkd56AD7mNC6enboeiK4ivI4g3l1Kfw5GcmA6ky7gye+f BoujZjVLlttu35WbLSt6QKhiHSEqNLWmAGFPHQ8idHdquIhoZZGNAvOl9MeEJ4siXeZi fFdT0RgKR8K2S/EcwztoPJwcaxDWy2hlXbbZXIvwq036pgQmYgJxcRft/Dp0N8TKpxPk uHCVXjji8lGyaDJgvqF9pVyCr4VshjO14zV8MS+OhvvsdkgSWooVvJNZjd4XAltPBlZD 7UtzTDabm33bKXeNbEMazop3zH0CubRn3hPwzX45ko0gBhpiLMbUECocTHT8i9vB2vRH I+5A== 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 s12si1892422pgg.188.2019.01.17.07.46.59; Thu, 17 Jan 2019 07:47:16 -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 S1727657AbfAQPpu (ORCPT + 99 others); Thu, 17 Jan 2019 10:45:50 -0500 Received: from mga06.intel.com ([134.134.136.31]:30748 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727093AbfAQPpu (ORCPT ); Thu, 17 Jan 2019 10:45:50 -0500 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2019 07:45:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,489,1539673200"; d="scan'208";a="117471042" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by fmsmga008.fm.intel.com with ESMTP; 17 Jan 2019 07:45:49 -0800 Date: Thu, 17 Jan 2019 08:44:37 -0700 From: Keith Busch To: Balbir Singh 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: [PATCHv4 00/13] Heterogeneuos memory node attributes Message-ID: <20190117154436.GB31543@localhost.localdomain> References: <20190116175804.30196-1-keith.busch@intel.com> <20190117125821.GF26056@350D> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190117125821.GF26056@350D> 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 Thu, Jan 17, 2019 at 11:58:21PM +1100, Balbir Singh wrote: > On Wed, Jan 16, 2019 at 10:57:51AM -0700, Keith Busch wrote: > > 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. > > > > Could you please expand on this text -- how are these attributes > exposed/consumed by both the kernel and user space? > > > This series' objective is to provide the attributes from such systems > > that are useful for applications to know about, and readily usable with > > existing tools and libraries. > > I presume these tools and libraries are numactl and mbind()? Yes, and numactl is used the examples provided in both changelogs and documentation in this series. Do you want to see those in the cover letter as well?