Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Alison Schofield <alison.schofield@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <iweiny@kernel.org>, Li Ming <ming.li@zohomail.com>,
	Richard Cheng <icheng@nvidia.com>
Cc: linux-cxl@vger.kernel.org
Subject: [PATCH 0/4] cxl/region: Update and test performance calculations
Date: Wed,  4 Nov 2026 19:28:27 -0800	[thread overview]
Message-ID: <cover.1793847269.git.alison.schofield@intel.com> (raw)

CXL regions expose latency and bandwidth through their access0 and access1
attributes. The same performance data also contributes to NUMA node access
coordinates and memory tier placement.

This series updates region performance calculation and reporting,
consolidates the completion-time operations, and adds cxl_test support
for validating the results.

This work was prompted by AI-assisted patch reviews that identified ways
stale contributions from failed or removed targets could affect region
performance data.

Patch 1 addresses stale contributions to region performance data by
recalculating from the attached targets only when the region completes.

Patch 2 makes region access attributes visible as soon as performance
data is available.

Patch 3 consolidates the three completion-time operations into one helper
shared by user-created and autodiscovered regions.

Patch 4 assigns distinct latency and bandwidth values to cxl_test memdevs
so that region performance calculations can be tested.

A new CXL unit test will be posted separately.
Testing with cxl_test:
- With all four patches, the new test and existing ndctl CXL tests pass.
- Without patch 1, rejected, cleared, and rebuilt target cases report
  incorrect latency or bandwidth.
- Without patch 2, the region access0 and access1 directories remain empty.

Based on v7.4-rc1.


Alison Schofield (4):
  cxl/region: Calculate performance data once all targets are attached
  cxl/region: Show access attributes once performance data is calculated
  cxl/region: Consolidate region performance completion
  cxl/test: Give each mock memdev its own performance data

 drivers/cxl/core/cdat.c      | 19 +++++++++++++++--
 drivers/cxl/core/region.c    | 40 +++++++++++++++++++++---------------
 drivers/cxl/cxl.h            |  3 +--
 tools/testing/cxl/test/cxl.c | 21 ++++++++++++++-----
 4 files changed, 57 insertions(+), 26 deletions(-)


base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
-- 
2.37.3


             reply	other threads:[~2026-11-05  3:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  3:28 Alison Schofield [this message]
2026-11-05  3:28 ` [PATCH 1/4] cxl/region: Calculate performance data once all targets are attached Alison Schofield
2026-11-06  5:51   ` Li Ming
2026-11-05  3:28 ` [PATCH 2/4] cxl/region: Show access attributes once performance data is calculated Alison Schofield
2026-11-06  6:11   ` Li Ming
2026-11-05  3:28 ` [PATCH 3/4] cxl/region: Consolidate region performance completion Alison Schofield
2026-11-06  6:15   ` Li Ming
2026-11-06 18:25     ` Alison Schofield
2026-11-10 13:07   ` Li Ming
2026-11-05  3:28 ` [PATCH 4/4] cxl/test: Give each mock memdev its own performance data Alison Schofield
2026-11-06  6:16   ` Li Ming
2026-11-10 18:31 ` [PATCH 0/4] cxl/region: Update and test performance calculations 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=cover.1793847269.git.alison.schofield@intel.com \
    --to=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=icheng@nvidia.com \
    --cc=iweiny@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --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