From: fan <nifan.cxl@gmail.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, jonathan.cameron@huawei.com,
dave@stgolabs.net
Subject: Re: [PATCH 1/3] cxl/region: Calculate performance data for a region
Date: Mon, 11 Dec 2023 09:44:24 -0800 [thread overview]
Message-ID: <ZXdKeOLQ8s0B08Eq@debian> (raw)
In-Reply-To: <170199190986.3543815.7111880145751330916.stgit@djiang5-mobl3>
On Thu, Dec 07, 2023 at 04:31:49PM -0700, Dave Jiang wrote:
> Calculate and store the performance data for a CXL region. Find the worst
> read and write latency for all the included ranges from each of the devices
> that attributes to the region and designate that as the latency data. Sum
> all the read and write bandwidth data for each of the device region and
> that is the total bandwidth for the region.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/cxl/core/region.c | 94 +++++++++++++++++++++++++++++++++++++++++++++
> drivers/cxl/cxl.h | 1
> 2 files changed, 95 insertions(+)
>
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 56e575c79bb4..d879f5702cf2 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -2934,6 +2934,98 @@ static int is_system_ram(struct resource *res, void *arg)
> return 1;
> }
>
> +static int cxl_region_perf_data_calculate(struct cxl_region *cxlr)
> +{
> + struct cxl_region_params *p = &cxlr->params;
> + struct cxl_endpoint_decoder *cxled;
> + unsigned int rd_bw = 0, rd_lat = 0;
> + unsigned int wr_bw = 0, wr_lat = 0;
> + struct access_coordinate *coord;
> + struct list_head *perf_list;
> + int rc = 0, i;
> +
> + lockdep_assert_held(&cxl_region_rwsem);
> +
> + /* No need to proceed if hmem attributes are already present */
> + if (cxlr->coord)
> + return 0;
> +
> + coord = devm_kzalloc(&cxlr->dev, sizeof(*coord), GFP_KERNEL);
> + if (!coord)
> + return -ENOMEM;
> +
> + cxled = p->targets[0];
cxled is only used in the for loop below, maybe we can move it into the loop.
Fan
> +
> + for (i = 0; i < p->nr_targets; i++) {
> + struct range dpa = {
> + .start = cxled->dpa_res->start,
> + .end = cxled->dpa_res->end,
> + };
> + struct cxl_memdev_state *mds;
> + struct perf_prop_entry *perf;
> + struct cxl_dev_state *cxlds;
> + struct cxl_memdev *cxlmd;
> + bool found = false;
> +
> + cxled = p->targets[i];
> + cxlmd = cxled_to_memdev(cxled);
> + cxlds = cxlmd->cxlds;
> + mds = to_cxl_memdev_state(cxlds);
> +
> + switch (cxlr->mode) {
> + case CXL_DECODER_RAM:
> + perf_list = &mds->ram_perf_list;
> + break;
> + case CXL_DECODER_PMEM:
> + perf_list = &mds->pmem_perf_list;
> + break;
> + default:
> + rc = -EINVAL;
> + goto err;
> + }
> +
> + if (list_empty(perf_list)) {
> + rc = -ENOENT;
> + goto err;
> + }
> +
> + list_for_each_entry(perf, perf_list, list) {
> + if (range_contains(&perf->dpa_range, &dpa)) {
> + found = true;
> + break;
> + }
> + }
> +
> + if (!found) {
> + rc = -ENOENT;
> + goto err;
> + }
> +
> + /* Get total bandwidth and the worst latency for the cxl region */
> + rd_lat = max_t(unsigned int, rd_lat,
> + perf->coord.read_latency);
> + rd_bw += perf->coord.read_bandwidth;
> + wr_lat = max_t(unsigned int, wr_lat,
> + perf->coord.write_latency);
> + wr_bw += perf->coord.write_bandwidth;
> + }
> +
> + *coord = (struct access_coordinate) {
> + .read_latency = rd_lat,
> + .read_bandwidth = rd_bw,
> + .write_latency = wr_lat,
> + .write_bandwidth = wr_bw,
> + };
> +
> + cxlr->coord = coord;
> +
> + return 0;
> +
> +err:
> + devm_kfree(&cxlr->dev, coord);
> + return rc;
> +}
> +
> static int cxl_region_probe(struct device *dev)
> {
> struct cxl_region *cxlr = to_cxl_region(dev);
> @@ -2959,6 +3051,8 @@ static int cxl_region_probe(struct device *dev)
> goto out;
> }
>
> + cxl_region_perf_data_calculate(cxlr);
> +
> /*
> * From this point on any path that changes the region's state away from
> * CXL_CONFIG_COMMIT is also responsible for releasing the driver.
> diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> index 004534cf0361..265da412c5bd 100644
> --- a/drivers/cxl/cxl.h
> +++ b/drivers/cxl/cxl.h
> @@ -529,6 +529,7 @@ struct cxl_region {
> struct cxl_pmem_region *cxlr_pmem;
> unsigned long flags;
> struct cxl_region_params params;
> + struct access_coordinate *coord;
> };
>
> struct cxl_nvdimm_bridge {
>
>
next prev parent reply other threads:[~2023-12-11 17:44 UTC|newest]
Thread overview: 21+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 23:30 [PATCH 1/3] cxl/region: Calculate performance data for a region Dave Jiang
2023-12-07 23:34 ` Dave Jiang
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=ZXdKeOLQ8s0B08Eq@debian \
--to=nifan.cxl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.