Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1944751imu; Thu, 10 Jan 2019 05:51:35 -0800 (PST) X-Google-Smtp-Source: ALg8bN6LI8Q1PvYV0223ZLsUBjvxXOfJsPqMeGucqbcCzy87V8AJSlwwT5s2re3UMuAyX8VY6ZTY X-Received: by 2002:aa7:84d3:: with SMTP id x19mr10235005pfn.220.1547128295822; Thu, 10 Jan 2019 05:51:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547128295; cv=none; d=google.com; s=arc-20160816; b=tmVNtSVUOHSrSBjK0Nycm2QZdi2a0d1Wix08qCKUagdrhET78yxQrIOYqTk6DbH2Z7 o877OKo1Gu8znfW0Pw3PK898B1Hl6cWtAydrVPkTHCiIKFnL2Q5inO/JZGfR59HSFLXY ytYX7MX3DDh90X6+nSTmtvctk1Ee8akuc6TvGCB9yWLMc+xttUtQej00uKUck2tKY333 Lqy0vYcPsNf2IZto7ADUB2srr/BalAjjTAPLz3ody62aiK7mQ4DyUvzzkuvosDmCqOGw TF5xnei12fwaBGbHi1q/Un4i0SiQdGLYxrZyoqqJSsAjv/Hny1PEThre7iF1eY1j1Xpn 1jHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:mime-version:date:references :in-reply-to:subject:cc:to:from; bh=idE3oWkaJgXKNp0T7oyW6bgT5hObsaT6ydf+POpPD/o=; b=uuZuGT36ZdS1ITf6lzqczoZXfuAuHDghfRUhfQTWH1p1BeHWm7kRorHwnfUK266+eJ Ke4+Ytcjd5TfQLe94JWat0l9aoOxqz1ZZPasePvr+ldMhZZgqs9YjTBOnc4aQGZOMWWU pHkpBwXoYtgu/+p/WyqJdnE4le6gc6XDV5nrubt4cz7xSuERv5nxkZrrwMQRimrpU56z Quihbw65DkHBNbwr45TPy5RiAewKXfYacaW1a9uZmnPWeBN6ncQ00ZaZIA/0g7wKcQCW 1ddA9X/1t7tyrs8Bs7g4/L0dJiussT1HXRqZ1ffmrLP5tw9sUwVT4UoB0DbuuQK4VFYL dluQ== 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=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c4si3831112pfi.110.2019.01.10.05.51.20; Thu, 10 Jan 2019 05:51:35 -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=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728426AbfAJMhP (ORCPT + 99 others); Thu, 10 Jan 2019 07:37:15 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:57280 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727944AbfAJMhO (ORCPT ); Thu, 10 Jan 2019 07:37:14 -0500 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id x0ACa0k9036627 for ; Thu, 10 Jan 2019 07:37:13 -0500 Received: from e06smtp05.uk.ibm.com (e06smtp05.uk.ibm.com [195.75.94.101]) by mx0a-001b2d01.pphosted.com with ESMTP id 2px4835m64-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 10 Jan 2019 07:37:12 -0500 Received: from localhost by e06smtp05.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 10 Jan 2019 12:37:10 -0000 Received: from b06cxnps4075.portsmouth.uk.ibm.com (9.149.109.197) by e06smtp05.uk.ibm.com (192.168.101.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 10 Jan 2019 12:37:07 -0000 Received: from b06wcsmtp001.portsmouth.uk.ibm.com (b06wcsmtp001.portsmouth.uk.ibm.com [9.149.105.160]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x0ACb6Wo65536032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 10 Jan 2019 12:37:06 GMT Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 50927A405F; Thu, 10 Jan 2019 12:37:06 +0000 (GMT) Received: from b06wcsmtp001.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4ABB0A405B; Thu, 10 Jan 2019 12:37:04 +0000 (GMT) Received: from skywalker.linux.ibm.com (unknown [9.199.54.61]) by b06wcsmtp001.portsmouth.uk.ibm.com (Postfix) with ESMTP; Thu, 10 Jan 2019 12:37:04 +0000 (GMT) X-Mailer: emacs 26.1 (via feedmail 11-beta-1 I) From: "Aneesh Kumar K.V" To: Keith Busch , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-mm@kvack.org Cc: Greg Kroah-Hartman , Rafael Wysocki , Dave Hansen , Dan Williams , Keith Busch Subject: Re: [PATCHv3 07/13] node: Add heterogenous memory access attributes In-Reply-To: <20190109174341.19818-8-keith.busch@intel.com> References: <20190109174341.19818-1-keith.busch@intel.com> <20190109174341.19818-8-keith.busch@intel.com> Date: Thu, 10 Jan 2019 18:07:02 +0530 MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-GCONF: 00 x-cbid: 19011012-0020-0000-0000-000003045E6F X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19011012-0021-0000-0000-0000215561FA Message-Id: <87y37sit8x.fsf@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-10_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901100103 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Keith Busch writes: > Heterogeneous memory systems provide memory nodes with different latency > and bandwidth performance attributes. Provide a new kernel interface for > subsystems to register the attributes under the memory target node's > initiator access class. If the system provides this information, applications > may query these attributes when deciding which node to request memory. > > The following example shows the new sysfs hierarchy for a node exporting > performance attributes: > > # tree -P "read*|write*" /sys/devices/system/node/nodeY/classZ/ > /sys/devices/system/node/nodeY/classZ/ > |-- read_bandwidth > |-- read_latency > |-- write_bandwidth > `-- write_latency > > The bandwidth is exported as MB/s and latency is reported in nanoseconds. > Memory accesses from an initiator node that is not one of the memory's > class "Z" initiator nodes may encounter different performance than > reported here. When a subsystem makes use of this interface, initiators > of a lower class number, "Z", have better performance relative to higher > class numbers. When provided, class 0 is the highest performing access > class. How does the definition of performance relate to bandwidth and latency here?. The initiator in this class has the least latency and high bandwidth? Can there be a scenario where both are not best for the same node? ie, for a target Node Y, initiator Node A gives the highest bandwidth but initiator Node B gets the least latency. How such a config can be represented? Or is that not possible? -aneesh