From: Christoph Lameter Date: Wed, 2 Oct 2024 17:27:00 +0000 (-0700) Subject: Add documentation for the new slab_strict_numa kernel command line option X-Git-Url: https://gentwo.org/gitweb/?a=commitdiff_plain;h=510a95b00355fcbf3fb9e0325c1a0f0ef80c6278;p=linux%2F.git Add documentation for the new slab_strict_numa kernel command line option Signed-off-by: Christoph Lameter (Ampere) --- diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index 1518343bbe22..89a4c0ec290c 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -6544,6 +6544,16 @@ stifb= [HW] Format: bpp:[:[:...]] + slab_strict_numa [MM] + Support memory policies on a per object level + in the slab allocator. The default is for memory + policies to be applied at the folio level when + a new folio is needed or a partial folio is + retrieved from the lists. Increases overhead + in the slab fastpaths but gains more accurate + NUMA kernel object placement which helps with slow + interconnects in NUMA systems. + strict_sas_size= [X86] Format: diff --git a/Documentation/mm/slub.rst b/Documentation/mm/slub.rst index 60d350d08362..84ca1dc94e5e 100644 --- a/Documentation/mm/slub.rst +++ b/Documentation/mm/slub.rst @@ -175,6 +175,15 @@ can be influenced by kernel parameters: ``slab_max_order`` to 0, what cause minimum possible order of slabs allocation. +``slab_strict_numa`` + Enables the application of memory policies on each + allocation. This results in more accurate placement of + objects which may result in the reduction of accesses + to remote nodes. The default is to only apply memory + policies at the folio level when a new folio is acquired + or a folio is retrieved from the lists. Enabling this + option reduces the fastpath performance of the slab allocator. + SLUB Debug output =================