From: Dave Jiang <dave.jiang@intel.com>
To: 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: [PATCH v8 0/3] cxl: Region bandwidth calculation for targets with shared upstream link
Date: Tue, 3 Sep 2024 17:11:49 -0700 [thread overview]
Message-ID: <20240904001316.1688225-1-dave.jiang@intel.com> (raw)
v8:
- Fixed kbot warning
- Fix checking incorrect return value (Alison)
- Remove goto from cxl_region-shared_upstream_bandwidth_update() (Alison)
- Add ** for kdoc comment (Alison)
- Fixup documentation texts (Jonathan)
- Rebase against v6.11-rc
This series provides recalculation of the CXL region bandwidth when the targets have
shared upstream link by walking the toplogy from bottom up and clamp the bandwdith
as the code traverses up the tree. An example topology:
An example topology from Jonathan:
CFMWS 0
|
_________|_________
| |
ACPI0017-0 ACPI0017-1
GP0/HB0/ACPI0016-0 GP1/HB1/ACPI0016-1
| | | |
RP0 RP1 RP2 RP3
| | | |
SW 0 SW 1 SW 2 SW 3
| | | | | | | |
EP0 EP1 EP2 EP3 EP4 EP5 EP6 EP7
Computation for the example topology:
Min (GP0 to CPU BW,
Min(SW 0 Upstream Link to RP0 BW,
Min(SW0SSLBIS for SW0DSP0 (EP0), EP0 DSLBIS, EP0 Upstream Link) +
Min(SW0SSLBIS for SW0DSP1 (EP1), EP1 DSLBIS, EP1 Upstream link)) +
Min(SW 1 Upstream Link to RP1 BW,
Min(SW1SSLBIS for SW1DSP0 (EP2), EP2 DSLBIS, EP2 Upstream Link) +
Min(SW1SSLBIS for SW1DSP1 (EP3), EP3 DSLBIS, EP3 Upstream link))) +
Min (GP1 to CPU BW,
Min(SW 2 Upstream Link to RP2 BW,
Min(SW2SSLBIS for SW2DSP0 (EP4), EP4 DSLBIS, EP4 Upstream Link) +
Min(SW2SSLBIS for SW2DSP1 (EP5), EP5 DSLBIS, EP5 Upstream link)) +
Min(SW 3 Upstream Link to RP3 BW,
Min(SW3SSLBIS for SW3DSP0 (EP6), EP6 DSLBIS, EP6 Upstream Link) +
Min(SW3SSLBIS for SW3DSP1 (EP7), EP7 DSLBIS, EP7 Upstream link))))
---
Dave Jiang (3):
cxl: Preserve the CDAT access_coordinate for an endpoint
cxl: Calculate region bandwidth of targets with shared upstream link
cxl: Add documentation to explain the shared link bandwidth calculation
Documentation/driver-api/cxl/access-coordinates.rst | 90 +++++++
Documentation/driver-api/cxl/index.rst | 1 +
MAINTAINERS | 1 +
drivers/cxl/core/cdat.c | 509 +++++++++++++++++++++++++++++++++++++++-
drivers/cxl/core/core.h | 4 +-
drivers/cxl/core/pci.c | 23 ++
drivers/cxl/core/port.c | 20 ++
drivers/cxl/core/region.c | 2 +
drivers/cxl/cxl.h | 1 +
drivers/cxl/cxlmem.h | 4 +-
10 files changed, 640 insertions(+), 15 deletions(-)
next reply other threads:[~2024-09-04 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 0:11 Dave Jiang [this message]
2024-09-04 0:11 ` [PATCH v8 1/3] cxl: Preserve the CDAT access_coordinate for an endpoint Dave Jiang
2024-09-04 0:11 ` [PATCH v8 2/3] cxl: Calculate region bandwidth of targets with shared upstream link Dave Jiang
2024-09-12 1:06 ` Alison Schofield
2024-09-04 0:11 ` [PATCH v8 3/3] cxl: Add documentation to explain the shared link bandwidth calculation Dave Jiang
2024-09-12 1:07 ` Alison Schofield
2024-09-21 10:26 ` [PATCH v8 0/3] cxl: Region bandwidth calculation for targets with shared upstream link 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=20240904001316.1688225-1-dave.jiang@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--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