From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by kanga.kvack.org (Postfix) with ESMTP id 154106B7D1A for ; Thu, 6 Dec 2018 18:38:43 -0500 (EST) Received: by mail-pf1-f200.google.com with SMTP id t2so1658141pfj.15 for ; Thu, 06 Dec 2018 15:38:43 -0800 (PST) Received: from mga14.intel.com (mga14.intel.com. [192.55.52.115]) by mx.google.com with ESMTPS id i69si1383878pgc.538.2018.12.06.15.38.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Dec 2018 15:38:42 -0800 (PST) Subject: Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind() References: <20181205001544.GR2937@redhat.com> <42006749-7912-1e97-8ccd-945e82cebdde@intel.com> <20181205021334.GB3045@redhat.com> <20181205175357.GG3536@redhat.com> <20181206192050.GC3544@redhat.com> <20181206223935.GG3544@redhat.com> <935fc14d-91f2-bc2a-f8b5-665e4145e148@deltatee.com> From: Dave Hansen Message-ID: <5e6c87d5-e4ef-12e7-32bf-c163f7ff58d7@intel.com> Date: Thu, 6 Dec 2018 15:38:41 -0800 MIME-Version: 1.0 In-Reply-To: <935fc14d-91f2-bc2a-f8b5-665e4145e148@deltatee.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Logan Gunthorpe , Jerome Glisse Cc: linux-mm@kvack.org, Andrew Morton , linux-kernel@vger.kernel.org, "Rafael J . Wysocki" , Matthew Wilcox , Ross Zwisler , Keith Busch , Dan Williams , Haggai Eran , Balbir Singh , "Aneesh Kumar K . V" , Benjamin Herrenschmidt , Felix Kuehling , Philip Yang , =?UTF-8?Q?Christian_K=c3=b6nig?= , Paul Blinzer , John Hubbard , Ralph Campbell , Michal Hocko , Jonathan Cameron , Mark Hairgrove , Vivek Kini , Mel Gorman , Dave Airlie , Ben Skeggs , Andrea Arcangeli , Rik van Riel , Ben Woodard , linux-acpi@vger.kernel.org On 12/6/18 3:28 PM, Logan Gunthorpe wrote: > I didn't think this was meant to describe actual real world performance > between all of the links. If that's the case all of this seems like a > pipe dream to me. The HMAT discussions (that I was a part of at least) settled on just trying to describe what we called "sticker speed". Nobody had an expectation that you *really* had to measure everything. The best we can do for any of these approaches is approximate things. > You're not *really* going to know bandwidth or latency for any of this > unless you actually measure it on the system in question. Yeah, agreed.