diff options
| author | Alison Schofield <alison.schofield@intel.com> | 2026-11-04 19:28:28 -0800 |
|---|---|---|
| committer | Dave Jiang <dave.jiang@intel.com> | 2026-11-10 10:51:51 -0700 |
| commit | 57f95cb59ffd2f276cc6e434982ec1dbfd614021 (patch) | |
| tree | 8cf89eb08ce4c983cb187ea422d45b2c8affe928 /scripts/Makefile.thinlto | |
| parent | 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4 (diff) | |
| download | linux-next-57f95cb59ffd2f276cc6e434982ec1dbfd614021.tar.gz linux-next-57f95cb59ffd2f276cc6e434982ec1dbfd614021.zip | |
cxl/region: Calculate performance data once all targets are attached
Region performance data is accumulated as endpoint decoders attempt to
join a region. Failed attachments and subsequently removed targets can
leave stale contributions in the region's performance coordinates.
Latency reflects the worst of all attempted targets, potentially
misreporting the region's access coordinates and affecting NUMA memory
tier placement. Bandwidth is normally recalculated when the region
completes, but if that calculation cannot be performed, the accumulated
bandwidth remains. Rebuilding a region can inflate it further.
Calculate performance data from the attached targets when the region
completes, for both user-created and autodiscovered regions. Reset the
coordinates before each calculation so only current members contribute.
Perform this calculation before the shared-upstream bandwidth update,
preserving the sum of member bandwidths if that update cannot complete.
Fixes: 3d9f4a197230 ("cxl/region: Calculate performance data for a region")
Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Li Ming <ming.li@zohomail.com>
Link: https://patch.msgid.link/2d2cd95e7e415c785dbd0cd627141a5a9f0731d6.1793847269.git.alison.schofield@intel.com
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
