From: Brice Goglin <brice.goglin@gmail.com>
To: Dave Jiang <dave.jiang@intel.com>, linux-cxl@vger.kernel.org
Cc: dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, alison.schofield@intel.com,
jonathan.cameron@huawei.com, dave@stgolabs.net
Subject: Re: [PATCH 2/3] cxl/region: Add sysfs attribute for locality attributes of CXL regions
Date: Mon, 11 Dec 2023 10:06:49 +0100 [thread overview]
Message-ID: <23a78aa8-e076-4b98-bd7c-4299aefd9895@gmail.com> (raw)
In-Reply-To: <170199191618.3543815.17768111410214136858.stgit@djiang5-mobl3>
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.
Brice
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> Documentation/ABI/testing/sysfs-bus-cxl | 40 +++++++++++++++++++++++++++++++
> drivers/cxl/core/region.c | 24 +++++++++++++++++++
> 2 files changed, 64 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-cxl b/Documentation/ABI/testing/sysfs-bus-cxl
> index fff2581b8033..e96f172eb6a6 100644
> --- a/Documentation/ABI/testing/sysfs-bus-cxl
> +++ b/Documentation/ABI/testing/sysfs-bus-cxl
> @@ -552,3 +552,43 @@ Description:
> attribute is only visible for devices supporting the
> capability. The retrieved errors are logged as kernel
> events when cxl_poison event tracing is enabled.
> +
> +
> +What: /sys/bus/cxl/devices/regionZ/read_bandwidth
> +Date: Apr, 2023
> +KernelVersion: v6.8
> +Contact: linux-cxl@vger.kernel.org
> +Description:
> + (RO) The aggregated read bandwidth of the region. The number is
> + the accumulated read bandwidth of all CXL memory devices that
> + contributes to the region.
> +
> +
> +What: /sys/bus/cxl/devices/regionZ/write_bandwidth
> +Date: Apr, 2023
> +KernelVersion: v6.8
> +Contact: linux-cxl@vger.kernel.org
> +Description:
> + (RO) The aggregated write bandwidth of the region. The number is
> + the accumulated write bandwidth of all CXL memory devices that
> + contributes to the region.
> +
> +
> +What: /sys/bus/cxl/devices/regionZ/read_latency
> +Date: Apr, 2023
> +KernelVersion: v6.8
> +Contact: linux-cxl@vger.kernel.org
> +Description:
> + (RO) The read latency of the region. The number is
> + the worst read latency of all CXL memory devices that
> + contributes to the region.
> +
> +
> +What: /sys/bus/cxl/devices/regionZ/write_latency
> +Date: Apr, 2023
> +KernelVersion: v6.8
> +Contact: linux-cxl@vger.kernel.org
> +Description:
> + (RO) The write latency of the region. The number is
> + the worst write latency of all CXL memory devices that
> + contributes to the region.
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index d879f5702cf2..72c47f624d63 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -645,6 +645,26 @@ static ssize_t size_show(struct device *dev, struct device_attribute *attr,
> }
> static DEVICE_ATTR_RW(size);
>
> +#define ACCESS_ATTR(attrib) \
> +static ssize_t attrib##_show(struct device *dev, \
> + struct device_attribute *attr, \
> + char *buf) \
> +{ \
> + struct cxl_region *cxlr = to_cxl_region(dev); \
> + \
> + if (!cxlr->coord) \
> + return 0; \
> + \
> + return sysfs_emit(buf, "%u\n", \
> + cxlr->coord->attrib); \
> +} \
> +static DEVICE_ATTR_RO(attrib)
> +
> +ACCESS_ATTR(read_bandwidth);
> +ACCESS_ATTR(read_latency);
> +ACCESS_ATTR(write_bandwidth);
> +ACCESS_ATTR(write_latency);
> +
> static struct attribute *cxl_region_attrs[] = {
> &dev_attr_uuid.attr,
> &dev_attr_commit.attr,
> @@ -653,6 +673,10 @@ static struct attribute *cxl_region_attrs[] = {
> &dev_attr_resource.attr,
> &dev_attr_size.attr,
> &dev_attr_mode.attr,
> + &dev_attr_read_bandwidth.attr,
> + &dev_attr_write_bandwidth.attr,
> + &dev_attr_read_latency.attr,
> + &dev_attr_write_latency.attr,
> NULL,
> };
>
>
>
>
next prev parent reply other threads:[~2023-12-11 9:06 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 [this message]
2023-12-12 19:30 ` Dave Jiang
2023-12-19 16:44 ` Jonathan Cameron
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=23a78aa8-e076-4b98-bd7c-4299aefd9895@gmail.com \
--to=brice.goglin@gmail.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.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