[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231203001501.126339-4-sxwjean@me.com>
Date: Sun, 3 Dec 2023 08:15:01 +0800
From: sxwjean@...com
To: vbabka@...e.cz, 42.hyeyoo@...il.com, cl@...ux.com,
linux-mm@...ck.org
Cc: penberg@...nel.org, rientjes@...gle.com, iamjoonsoo.kim@....com,
roman.gushchin@...ux.dev, corbet@....net, keescook@...omium.org,
arnd@...db.de, akpm@...ux-foundation.org,
gregkh@...uxfoundation.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Xiongwei Song <xiongwei.song@...driver.com>
Subject: [PATCH v2 3/3] mm/slub: correct the default value of slub_min_objects in doc
From: Xiongwei Song <xiongwei.song@...driver.com>
There is no a value assigned to slub_min_objects by default, it always
is 0 that is initialized by compiler if no assigned value by command line.
min_objects is calculated based on processor numbers in calculate_order().
For more details, see commit 9b2cd506e5f2 ("slub: Calculate min_objects
based on number of processors.")
Signed-off-by: Xiongwei Song <xiongwei.song@...driver.com>
---
Documentation/mm/slub.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/mm/slub.rst b/Documentation/mm/slub.rst
index be75971532f5..1f4399581449 100644
--- a/Documentation/mm/slub.rst
+++ b/Documentation/mm/slub.rst
@@ -150,7 +150,7 @@ list_lock once in a while to deal with partial slabs. That overhead is
governed by the order of the allocation for each slab. The allocations
can be influenced by kernel parameters:
-.. slub_min_objects=x (default 4)
+.. slub_min_objects=x (default 0)
.. slub_min_order=x (default 0)
.. slub_max_order=x (default 3 (PAGE_ALLOC_COSTLY_ORDER))
--
2.34.1
Powered by blists - more mailing lists