From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dan.j.williams@intel.com>,
<ira.weiny@intel.com>, <vishal.l.verma@intel.com>,
<alison.schofield@intel.com>
Subject: Re: [PATCH v5 08/14] cxl: Compute the entire CXL path latency and bandwidth data
Date: Fri, 12 May 2023 16:09:01 +0100 [thread overview]
Message-ID: <20230512160901.00001384@Huawei.com> (raw)
In-Reply-To: <168357886214.2756219.978696616095404572.stgit@djiang5-mobl3>
On Mon, 08 May 2023 13:47:42 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> CXL Memory Device SW Guide rev1.0 2.11.2 provides instruction on how to
> caluclate latency and bandwidth for CXL memory device. Calculate minimum
Spell check.
Also, a link for SW guide probably good to add.
> bandwidth and total latency for the path from the CXL device to the root
> port. The QTG id is retrieved by providing the performance data as input
> and calling the root port callback ->get_qos_class(). The retrieved id is
> stored with the cxl_port of the CXL device.
>
> For example for a device that is directly attached to a host bus:
> Total Latency = Device Latency (from CDAT) + Dev to Host Bus (HB) Link
> Latency + Generic Port Latency
> Min Bandwidth = Min bandwidth for link bandwidth between HB
> and CXL device, device CDAT bandwidth, and Generic Port
> Bandwidth
>
> For a device that has a switch in between host bus and CXL device:
> Total Latency = Device (CDAT) Latency + Dev to Switch Link Latency +
> Switch (CDAT) Latency + Switch to HB Link Latency +
> Generic Port Latency
> Min Bandwidth = Min bandwidth for link bandwidth between CXL device
> to CXL switch, CXL device CDAT bandwidth, CXL switch CDAT
> bandwidth, CXL switch to HB bandwidth, and Generic Port
> Bandwidth.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> ---
> v5:
> - Use new API call cxl_endpoint_get_perf_coordinates().
> - Use root_port->get_qos_class() (Dan)
> - Add endieness handling to DSM input.
> ---
> drivers/cxl/cxl.h | 1 +
> drivers/cxl/port.c | 56 +++++++++++++++++++++++++++++++++++++++++++++++++---
> 2 files changed, 54 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index 0c8952e568cc..7c94f07771c1 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -833,6 +833,7 @@ struct dsmas_entry {
> struct range dpa_range;
> u8 handle;
> struct access_coordinate coord;
> + int qos_class;
> };
>
> #ifdef CONFIG_ACPI
> diff --git a/drivers/cxl/port.c b/drivers/cxl/port.c
> index c5a24b75bf03..b474997cc7ee 100644
> --- a/drivers/cxl/port.c
> +++ b/drivers/cxl/port.c
> @@ -67,6 +67,52 @@ static void dsmas_list_destroy(struct list_head *dsmas_list)
> }
> }
>
> +static int cxl_port_perf_data_calculate(struct cxl_port *port,
> + struct list_head *dsmas_list)
> +{
> + struct access_coordinate c;
> + struct qtg_dsm_input input;
> + struct cxl_port *root_port;
> + struct cxl_root *cxl_root;
> + struct dsmas_entry *dent;
> + int rc, qos_class;
> +
> + rc = cxl_endpoint_get_perf_coordinates(port, &c);
> + if (rc) {
> + dev_dbg(&port->dev, "Failed to retrieve perf coordinates.\n");
> + return rc;
> + }
> +
> + root_port = find_cxl_root(port);
> + cxl_root = to_cxl_root(root_port);
> + if (!cxl_root->ops && !cxl_root->ops->get_qos_class)
> + return -EOPNOTSUPP;
> +
> + list_for_each_entry(dent, dsmas_list, list) {
> + dent->coord.read_latency = dent->coord.read_latency +
> + c.read_latency;
> + dent->coord.write_latency = dent->coord.write_latency +
> + c.write_latency;
> + dent->coord.read_bandwidth = min_t(int, c.read_bandwidth,
> + dent->coord.read_bandwidth);
> + dent->coord.write_bandwidth = min_t(int, c.write_bandwidth,
> + dent->coord.write_bandwidth);
> +
> + input.rd_lat = cpu_to_le32(dent->coord.read_latency);
> + input.wr_lat = cpu_to_le32(dent->coord.write_latency);
> + input.rd_bw = cpu_to_le32(dent->coord.read_bandwidth);
> + input.wr_bw = cpu_to_le32(dent->coord.write_bandwidth);
> +
> + qos_class = cxl_root->ops->get_qos_class(root_port, &input);
> + if (qos_class < 0)
> + continue;
> +
> + dent->qos_class = qos_class;
> + }
> +
> + return 0;
> +}
> +
> static int cxl_switch_port_probe(struct cxl_port *port)
> {
> struct cxl_hdm *cxlhdm;
> @@ -155,10 +201,14 @@ static int cxl_endpoint_port_probe(struct cxl_port *port)
> LIST_HEAD(dsmas_list);
>
> rc = cxl_cdat_endpoint_process(port, &dsmas_list);
> - if (rc < 0)
> + if (rc < 0) {
> dev_dbg(&port->dev, "Failed to parse CDAT: %d\n", rc);
> -
> - /* Performance data processing */
> + } else {
> + rc = cxl_port_perf_data_calculate(port, &dsmas_list);
> + if (rc)
> + dev_dbg(&port->dev,
> + "Failed to do perf coord calculations.\n");
> + }
>
> dsmas_list_destroy(&dsmas_list);
> }
>
>
next prev parent reply other threads:[~2023-05-12 15:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 20:46 [PATCH v5 00/14] cxl: Add support for QTG ID retrieval for CXL subsystem Dave Jiang
2023-05-08 20:46 ` [PATCH v5 01/14] cxl: Add callback to parse the DSMAS subtables from CDAT Dave Jiang
2023-05-12 14:26 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 02/14] cxl: Add callback to parse the DSLBIS subtable " Dave Jiang
2023-05-12 14:33 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 03/14] cxl: Add callback to parse the SSLBIS " Dave Jiang
2023-05-12 14:41 ` Jonathan Cameron
2023-05-16 17:49 ` Dave Jiang
2023-05-08 20:47 ` [PATCH v5 04/14] cxl: Add support for _DSM Function for retrieving QTG ID Dave Jiang
2023-05-12 14:50 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 05/14] cxl: Calculate and store PCI link latency for the downstream ports Dave Jiang
2023-05-08 20:47 ` [PATCH v5 06/14] cxl: Store the access coordinates for the generic ports Dave Jiang
2023-05-12 14:59 ` Jonathan Cameron
2023-05-16 20:58 ` Dave Jiang
2023-05-16 21:13 ` Dan Williams
2023-05-16 21:52 ` Dave Jiang
2023-05-08 20:47 ` [PATCH v5 07/14] cxl: Add helper function that calculate performance data for downstream ports Dave Jiang
2023-05-12 15:05 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 08/14] cxl: Compute the entire CXL path latency and bandwidth data Dave Jiang
2023-05-12 15:09 ` Jonathan Cameron [this message]
2023-05-08 20:47 ` [PATCH v5 09/14] cxl: Wait Memory_Info_Valid before access memory related info Dave Jiang
2023-05-12 15:16 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 10/14] cxl: Move identify and partition query from pci probe to port probe Dave Jiang
2023-05-12 15:17 ` Jonathan Cameron
2023-05-08 20:47 ` [PATCH v5 11/14] cxl: Move read_cdat_data() to after media is ready Dave Jiang
2023-05-12 15:18 ` Jonathan Cameron
2023-05-08 20:48 ` [PATCH v5 12/14] cxl: Store QTG IDs and related info to the CXL memory device context Dave Jiang
2023-05-12 15:30 ` Jonathan Cameron
2023-05-08 20:48 ` [PATCH v5 13/14] cxl: Export sysfs attributes for memory device QoS class Dave Jiang
2023-05-12 15:33 ` Jonathan Cameron
2023-05-08 20:48 ` [PATCH v5 14/14] cxl/mem: Add debugfs output for QTG related data Dave Jiang
2023-05-12 15:36 ` Jonathan Cameron
2023-05-17 22:28 ` Dave Jiang
2023-05-12 15:28 ` [PATCH v5 00/14] cxl: Add support for QTG ID retrieval for CXL subsystem Jonathan Cameron
2023-05-16 21:49 ` Dan Williams
2023-05-17 8:50 ` Jonathan Cameron
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=20230512160901.00001384@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--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