From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Cc: vishal.l.verma@intel.com
Subject: [NDCTL PATCH v6 0/4] ndctl: Add support of qos_class for CXL CLI
Date: Wed, 7 Feb 2024 10:19:35 -0700 [thread overview]
Message-ID: <20240207172055.1882900-1-dave.jiang@intel.com> (raw)
Hi Vishal,
With the QoS class series merged to the v6.8 kernel, can you please review and
apply this series to ndctl if acceptable?
v6:
- Check return value of create_region_validate_qos_class() (Wonjae)
v5:
- split out test from cxl-topology.sh (Vishal)
v4:
- Update against changes in kernel from multi to single qos_class entry
- Add test in cxl-topology.sh (Dan)
- See individual patch log for details
v3:
- Rebase against latest ndctl/pending branch.
The series adds support for the kernel enabling of QoS class in the v6.8
kernel. The kernel exports a qos_class token for the root decoders (CFMWS) and as
well as for the CXL memory devices. The qos_class exported for a device is
calculated by the driver during device probe. Currently a qos_class is exported
for the volatile partition (ram) and another for the persistent partition (pmem).
In the future qos_class will be exported for DCD regions. Display of qos_class is
through the CXL CLI list command with -vvv for extra verbose.
A qos_class check as also been added for region creation. A warning is emitted
when the qos_class of a memory range of a CXL memory device being included in
the CXL region assembly does not match the qos_class of the root decoder. Options
are available to suppress the warning or to fail the region creation. This
enabling provides a guidance on flagging memory ranges being used is not
optimal for performance for the CXL region to be formed.
next reply other threads:[~2024-02-07 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:19 Dave Jiang [this message]
2024-02-07 17:19 ` [NDCTL PATCH v6 1/4] ndctl: cxl: Add QoS class retrieval for the root decoder Dave Jiang
2024-02-07 20:05 ` Alison Schofield
2024-02-07 20:13 ` Alison Schofield
2024-02-07 20:16 ` Dave Jiang
2024-02-07 20:24 ` Verma, Vishal L
2024-02-07 17:19 ` [NDCTL PATCH v6 2/4] ndctl: cxl: Add QoS class support for the memory device Dave Jiang
2024-02-07 17:19 ` [NDCTL PATCH v6 3/4] ndctl: cxl: add QoS class check for CXL region creation Dave Jiang
2024-02-07 21:02 ` Verma, Vishal L
2024-02-07 23:32 ` Dave Jiang
2024-02-07 17:19 ` [NDCTL PATCH v6 4/4] ndctl: add test for qos_class in CXL test suite Dave Jiang
2024-02-07 21:05 ` Verma, Vishal L
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=20240207172055.1882900-1-dave.jiang@intel.com \
--to=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).