From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, dave@stgolabs.net,
jonathan.cameron@huawei.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com, gourry@gourry.net
Subject: Re: [PATCH v2 0/3] cxl: Update CXL documentation for access coordinates calculation
Date: Thu, 15 May 2025 10:25:57 -0700 [thread overview]
Message-ID: <97aa4fee-1f3c-4817-95cb-5393a800432c@intel.com> (raw)
In-Reply-To: <aCYhFjRzZNNlFfvJ@aschofie-mobl2.lan>
On 5/15/25 10:15 AM, Alison Schofield wrote:
> On Wed, May 14, 2025 at 05:09:20PM -0700, Dave Jiang wrote:
>> v2:
>> - Language clarifications (Gregory)
>> - Move all CDAT bits into single document. (Gregory)
>> - Define CDAT terms. (Gregory)
>>
>> Add CXL access coordinates calculation documentation including CDAT details.
>
> I appreciate this documentation and it makes me half-smart on this
> stuff which leads to my possibly annoying questions:
>
> Say I have a BIOS defined region. Can I look at the result of these
> calcs and see, or judge, whether BIOS set up the most efficient
> region?
Yes I think you can, since we do the calculation for all devices, not just the hot-plugged ones.
>
> For a user created region where the topology offers some flexibility,
> can a user predict these numbers before creating a region? Can the
> user create a region, evaluate its 'perf characteristics', then destroy
> it and try another flavor?
I think so. If the QOS class mismatches, I believe you'll get a warning from CXL CLI, but you can override.
>
> I realize this is internal docs on driver behavior and not user
> space documentation. I'm looking for info to improve my understanding
> not suggesting this info belongs in these docs.
>
> Thanks - and, for the series:
>
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
>>
>>
>> Dave Jiang (3):
>> cxl: docs/platform/cdat reference documentation
>> cxl: docs/platform/acpi/srat Add generic target documentation
>> cxl: doc/linux/access-coordinates Update access coordinates
>> calculation methods
>>
>> Documentation/driver-api/cxl/index.rst | 1 +
>> .../cxl/linux/access-coordinates.rst | 86 +++++++++++++
>> .../driver-api/cxl/platform/acpi/srat.rst | 27 ++++
>> .../driver-api/cxl/platform/cdat.rst | 118 ++++++++++++++++++
>> 4 files changed, 232 insertions(+)
>> create mode 100644 Documentation/driver-api/cxl/platform/cdat.rst
>>
>>
>> base-commit: 7855bc1362518673103bd9357827572207e6f6d9
>> --
>> 2.49.0
>>
next prev parent reply other threads:[~2025-05-15 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 0:09 [PATCH v2 0/3] cxl: Update CXL documentation for access coordinates calculation Dave Jiang
2025-05-15 0:09 ` [PATCH v2 1/3] cxl: docs/platform/cdat reference documentation Dave Jiang
2025-05-15 3:41 ` Gregory Price
2025-05-15 0:09 ` [PATCH v2 2/3] cxl: docs/platform/acpi/srat Add generic target documentation Dave Jiang
2025-05-15 0:09 ` [PATCH v2 3/3] cxl: doc/linux/access-coordinates Update access coordinates calculation methods Dave Jiang
2025-05-15 17:15 ` [PATCH v2 0/3] cxl: Update CXL documentation for access coordinates calculation Alison Schofield
2025-05-15 17:25 ` Dave Jiang [this message]
2025-05-15 23:51 ` Dave Jiang
2025-05-19 15:42 ` Jonathan Cameron
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=97aa4fee-1f3c-4817-95cb-5393a800432c@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox