linuxmsm/laptops-kernel
0
0
Fork 0
mirror of https://github.com/linux-msm/laptops-kernel.git synced 2026-08-13 14:19:53 -07:00
Code Issues Packages Projects Releases Wiki Activity

cxl: docs/linux/dax-driver - fix typos

Browse Source 
Fix two obvious typos in the "kmem conversion" section.

Signed-off-by: Zenghui Yu <zenghui.yu@linux.dev>
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Dongliang Mu <dzm91@hust.edu.cn>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Link: https://patch.msgid.link/20260614161458.88942-1-zenghui.yu@linux.dev
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
This commit is contained in:
Zenghui Yu
2026-06-29 08:40:06 -07:00
committed by Dave Jiang
parent fe7883d0e9
commit a667f1eb71
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/driver-api/cxl/linux/dax-driver.rst
+2 -2
View File
@@ -35,9 +35,9 @@ will be exposed to the kernel page allocator in the user-selected memory
zone.
The :code:`memmap_on_memory` setting (both global and DAX device local)
dictates where the kernell will allocate the :code:`struct folio` descriptors
dictates where the kernel will allocate the :code:`struct folio` descriptors
for this memory will come from. If :code:`memmap_on_memory` is set, memory
hotplug will set aside a portion of the memory block capacity to allocate
folios. If unset, the memory is allocated via a normal :code:`GFP_KERNEL`
allocation - and as a result will most likely land on the local NUM node of the
allocation - and as a result will most likely land on the local NUMA node of the
CPU executing the hotplug operation.