Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp954861rwd; Thu, 15 Jun 2023 04:36:05 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4dezfj9z3d2ek7tW/pUTbqKkIQCsLhoKl3BkVBN03i2YtjNwWX6hMcuadr5ArjLsh5cvdK X-Received: by 2002:a05:6402:10d8:b0:50b:c630:a956 with SMTP id p24-20020a05640210d800b0050bc630a956mr10188443edu.17.1686828965548; Thu, 15 Jun 2023 04:36:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686828965; cv=none; d=google.com; s=arc-20160816; b=Jkmh2QIy+K+LY8HgP3BigKypC75YM4xVS5nvbkz86guiE1vt9UNgGU0JX/zuBpTUdg JFJlHf6p7NjayMw8VlRcBW6a/fNd/ZVjDeuyOBPrpqRud2oaiTEpOQ4h+c6l/z1RBQE/ zoayuzBnp/qiUGQ5/h8YJsGu6ecICRT2WAUzpBaXI7uO+An67Edj5hIzzYyOAJLIB4SV aovTJ+5AFShQ8DWtq3e53r8Jr4V3HpxY/adYE/Nt12DkdAPE81GamqrQAdLp6OZF1znk Iro8XTa+k6NpTpKI+mSFZFVO5kVFefHWBfP915Y3s8JDMNOEgY7UROKIizuzchTh6PAe kJXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=T7z06B3Awz3Z7V6Fhs+BgacpgDXNnud0TtunS8F3XxE=; b=Kdillyhmf8Xq1obfI9nLcLSl9WedUaO7ncLCa6NlOw0n4hs8lzHiyfYVrTU6KLuTyp yWsrZ7Cact4Bjp5g0NIx14U4TjbSpP1NK1275TOFAPr2MNYbicrX+Zg+k2do/WzwRMFm +M/PZoseVIBGfVkziQr4TaL0yeZoc6hoDmkUfzxHGwy9CrgYF/j7wpRs6wf9C0fVjM99 GrLzuLA9v8I3i42pjtc8HwmEm3Y0dm0Gv0eGpSuV2nQGvk9mu0ZDVshPc/w4kz3JFb05 uSvDG4/xaUIXX8nKIY7qGruVFxzY45Xc5mp212lbv4x1PkSwoBeY4qPmwZjEX4vTUtKp WUIQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=zbspOMrK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w6-20020aa7da46000000b00514a41ff0casi6205387eds.216.2023.06.15.04.35.40; Thu, 15 Jun 2023 04:36:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=zbspOMrK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245160AbjFOLYs (ORCPT + 99 others); Thu, 15 Jun 2023 07:24:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47100 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236141AbjFOLYq (ORCPT ); Thu, 15 Jun 2023 07:24:46 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A3982695; Thu, 15 Jun 2023 04:24:45 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9DCDB622B5; Thu, 15 Jun 2023 11:24:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B6A3AC433C0; Thu, 15 Jun 2023 11:24:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1686828284; bh=PmOSshALTtpzFoSkBJCRXqWkU0jVVespwvFelGEXXuA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=zbspOMrKa7NW/fRHDWJohcs5Hb8lHjF7SOkt4GQA9ChKo64ZSr83ayCQBVTGstHur JmUPgfnHX8aBDD0PJIc0oZ6epOeyZBiZSQlZgwi5okLzBvLcCwZygtPBx1rPoi2maj 5G59+oMlrtJJ2x3xxs8KHPawzzfhlPbOnhzqEzdU= Date: Thu, 15 Jun 2023 13:24:41 +0200 From: Greg KH To: Dave Jiang Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, linux-cxl@vger.kernel.org, Dan Williams , rafael@kernel.org, jonathan.cameron@huawei.com Subject: Re: [PATCH v2] base/node / acpi: Change 'node_hmem_attrs' to 'access_coordinates' Message-ID: <2023061533-paralyze-tinker-3d32@gregkh> References: <168660916231.1965241.248859226126456131.stgit@djiang5-mobl3> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <168660916231.1965241.248859226126456131.stgit@djiang5-mobl3> X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 12, 2023 at 03:32:42PM -0700, Dave Jiang wrote: > Dan Williams suggested changing the struct 'node_hmem_attrs' to > 'access_coordinates' [1]. The struct is a container of r/w-latency and > r/w-bandwidth numbers. Moving forward, this container will also be used by > CXL to store the performance characteristics of each link hop in > the PCIE/CXL topology. So, where node_hmem_attrs is just the access > parameters of a memory-node, access_coordinates applies more broadly > to hardware topology characteristics. The observation is that seemed like > an excercise in having the application identify "where" it falls on a > spectrum of bandwidth and latency needs. For the tuple of read/write-latency > and read/write-bandwidth, "coordinates" is not a perfect fit. Sometimes it > is just conveying values in isolation and not a "location" relative to > other performance points, but in the end this data is used to identify the > performance operation point of a given memory-node. [2] > > Link: http://lore.kernel.org/r/64471313421f7_1b66294d5@dwillia2-xfh.jf.intel.com.notmuch/ > Link: https://lore.kernel.org/linux-cxl/645e6215ee0de_1e6f2945e@dwillia2-xfh.jf.intel.com.notmuch/ > Suggested-by: Dan Williams > Reviewed-by: Dan Williams > Signed-off-by: Dave Jiang > > --- > > Hi Greg and Rafael, > please consider ACK this patch and Dan can take it through the > CXL upstream tree. The remaining ACPI [1] and CXL [2] patches for enabling > CXL QoS class data have dependency on this patch. Thank you! > > [1]: https://lore.kernel.org/linux-cxl/168333141100.2290593.16294670316057617744.stgit@djiang5-mobl3/T/#t > [2]: https://lore.kernel.org/linux-cxl/168451588868.3470703.3527256859632103687.stgit@djiang5-mobl3/T/#t Acked-by: Greg Kroah-Hartman