From: Alison Schofield <alison.schofield@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-pci@vger.kernel.org,
dan.j.williams@intel.com, ira.weiny@intel.com,
vishal.l.verma@intel.com, Jonathan.Cameron@huawei.com,
dave@stgolabs.net
Subject: Re: [PATCH v3 0/2] cxl: Region bandwidth calculation for targets with shared upstream link
Date: Wed, 5 Jun 2024 11:38:38 -0700 [thread overview]
Message-ID: <ZmCwrk5MGnnHxmKV@aschofie-mobl2> (raw)
In-Reply-To: <20240529214357.1193417-1-dave.jiang@intel.com>
On Wed, May 29, 2024 at 02:38:56PM -0700, Dave Jiang wrote:
> 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 trasverses up the tree. An example topology:
>
> An example topology from Jonathan:
>
> CFMWS 0
> |
> _________|_________
> | |
> GP0/HB0/ACPI0017-0 GP1/HB1/ACPI0017-1
> | | | |
> RP0 RP1 RP2 RP3
> | | | |
> SW 0 SW 1 SW 2 SW 3
> | | | | | | | |
> EP0 EP1 EP2 EP3 EP4 EP5 EP6 EP7
Are the ACPI0017 labels a typo?
Expected host bridges to be labelled as ACPI0016's.
That's all, just did a drive-by on the art today.
-- Alison
next prev parent reply other threads:[~2024-06-05 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 21:38 [PATCH v3 0/2] cxl: Region bandwidth calculation for targets with shared upstream link Dave Jiang
2024-05-29 21:38 ` [PATCH v3 1/2] cxl: Preserve the CDAT access_coordinate for an endpoint Dave Jiang
2024-05-29 21:38 ` [PATCH v3 2/2] cxl: Calculate region bandwidth of targets with shared upstream link Dave Jiang
2024-06-05 14:19 ` Jonathan Cameron
2024-06-05 18:05 ` Dave Jiang
2024-06-06 23:39 ` Dave Jiang
2024-06-07 14:30 ` Jonathan Cameron
2024-06-07 16:12 ` Dave Jiang
2024-06-07 17:58 ` Jonathan Cameron
2024-06-05 18:38 ` Alison Schofield [this message]
2024-06-06 23:27 ` [PATCH v3 0/2] cxl: Region bandwidth calculation for " Dave Jiang
2024-06-06 23:46 ` 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=ZmCwrk5MGnnHxmKV@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@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