From: Gregory Price <gourry@gourry.net>
To: rakuram <rakuram.e96@gmail.com>
Cc: linux-doc@vger.kernel.org, dan.j.williams@intel.com,
dave@stgolabs.net, dave.jiang@intel.com,
jonathan.cameron@huawei.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, linux-cxl@vger.kernel.org,
alison.schofield@intel.com, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org, corbet@lwn.net
Subject: Re: [PATCH] Documentation/driver-api: Fix typo error in cxl
Date: Sun, 17 Aug 2025 13:04:10 -0400 [thread overview]
Message-ID: <aKILiuYaijqAZvPR@fedora> (raw)
In-Reply-To: <20250816183034.7970-1-rakuram.e96@gmail.com>
On Sun, Aug 17, 2025 at 12:00:33AM +0530, rakuram wrote:
> diff --git a/Documentation/driver-api/cxl/allocation/page-allocator.rst b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> index 7b8fe1b8d5bb..4ac3368c3947 100644
> --- a/Documentation/driver-api/cxl/allocation/page-allocator.rst
> +++ b/Documentation/driver-api/cxl/allocation/page-allocator.rst
> @@ -62,7 +62,7 @@ Because the local node does not have :code:`ZONE_MOVABLE`, the CXL node is
> functionally unreachable for direct allocation. As a result, the only way
> for CXL capacity to be used is via `demotion` in the reclaim path.
>
> -This configuration also means that if the DRAM ndoe has :code:`ZONE_MOVABLE`
> +This configuration also means that if the DRAM node has :code:`ZONE_MOVABLE`
> capacity - when that capacity is depleted, the page allocator will actually
> prefer CXL :code:`ZONE_MOVABLE` pages over DRAM :code:`ZONE_NORMAL` pages.
>
I have since discovered that this area of documentation is incorrect,
and this behavior is the result of bad reclaim logic. I will rewrite
this area shortly.
Just drop the page-allocator.rst chunk please.
Reviewed-by: Gregory Price <gourry@gourry.net>
~Gregory
next prev parent reply other threads:[~2025-08-17 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 18:30 [PATCH] Documentation/driver-api: Fix typo error in cxl rakuram
2025-08-16 20:20 ` Randy Dunlap
2025-08-17 17:04 ` Gregory Price [this message]
2025-08-17 17:50 ` rakuram
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 8:41 Moktar SELLAMI
2025-08-19 11:28 ` Jonathan Cameron
2025-08-19 17:23 ` Randy Dunlap
2025-08-29 22:35 ` Jonathan Corbet
2025-08-31 23:07 ` Moktar sellami
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=aKILiuYaijqAZvPR@fedora \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=rakuram.e96@gmail.com \
--cc=skhan@linuxfoundation.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