From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Brice Goglin <brice.goglin@gmail.com>,
<linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<ira.weiny@intel.com>, <vishal.l.verma@intel.com>,
<alison.schofield@intel.com>, <dave@stgolabs.net>
Subject: Re: [PATCH 2/3] cxl/region: Add sysfs attribute for locality attributes of CXL regions
Date: Tue, 19 Dec 2023 16:44:08 +0000 [thread overview]
Message-ID: <20231219164408.0000790a@Huawei.com> (raw)
In-Reply-To: <500b0900-f4bb-475d-817b-6a72f18e0134@intel.com>
On Tue, 12 Dec 2023 12:30:47 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> On 12/11/23 02:06, Brice Goglin wrote:
> > Le 08/12/2023 à 00:31, Dave Jiang a écrit :
> >> Add read/write latencies and bandwidth sysfs attributes for the enabled CXL
> >> region. The bandwidth is the aggregated bandwidth of all devices that
> >> contributes to the CXL region. The latency is the worst latency of the
> >> device amongst all the devices that contributes to the CXL region.
> >
> >
> > Hello
> >
> > Which initiator do these bandwidths/latencies refer to? Local CPUs near the root port? This should be specified in the doc.
>
> Currently I'm only storing the numbers from initiator pxm 0 to these targets in the hmat target list. I'm open to suggestions as to if a different way would be better.
Nearest node with CPUs would be better I think.
Jonathan
next prev parent reply other threads:[~2023-12-19 16:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 23:31 [PATCH 0/3] cxl: Add support to report region access coordinates to numa nodes Dave Jiang
2023-12-07 23:31 ` [PATCH 1/3] cxl/region: Calculate performance data for a region Dave Jiang
2023-12-11 17:44 ` fan
2023-12-12 0:19 ` Dan Williams
2023-12-07 23:31 ` [PATCH 2/3] cxl/region: Add sysfs attribute for locality attributes of CXL regions Dave Jiang
2023-12-11 9:06 ` Brice Goglin
2023-12-12 19:30 ` Dave Jiang
2023-12-19 16:44 ` Jonathan Cameron [this message]
2023-12-20 20:26 ` Dave Jiang
2023-12-21 18:23 ` Dave Jiang
2023-12-11 18:03 ` fan
2023-12-11 18:13 ` Dave Jiang
2023-12-11 18:27 ` fan
2023-12-12 0:23 ` Dan Williams
2023-12-12 13:46 ` Brice Goglin
2023-12-12 16:00 ` Dave Jiang
2023-12-07 23:32 ` [PATCH 3/3] cxl: Add memory hotplug notifier for cxl region Dave Jiang
2023-12-08 3:35 ` Huang, Ying
2023-12-12 0:30 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231219164408.0000790a@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=brice.goglin@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox