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@xxxxxxxxxx> ~Gregory
