mm/Kconfig: correct description of DEFERRED_STRUCT_PAGE_INIT

The description mentions kswapd threads, while the deferred struct page
initialization is actually done by one-off "pgdatinitX" threads.

Fix the description so that potentially users are not confused about
pgdatinit threads using CPU after boot instead of kswapd.

Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

1 files changed, 5 insertions, 4 deletions

diff --git a/mm/Kconfig b/mm/Kconfig
index 97a4e06b15c0..03cbfa072f42 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -624,7 +624,7 @@ config ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT
         bool
 
 config DEFERRED_STRUCT_PAGE_INIT
-        bool "Defer initialisation of struct pages to kswapd"
+        bool "Defer initialisation of struct pages to kthreads"
         default n
         depends on ARCH_SUPPORTS_DEFERRED_STRUCT_PAGE_INIT
         depends on MEMORY_HOTPLUG
@@ -633,9 +633,10 @@ config DEFERRED_STRUCT_PAGE_INIT
           single thread. On very large machines this can take a considerable
           amount of time. If this option is set, large machines will bring up
           a subset of memmap at boot and then initialise the rest in parallel
-          when kswapd starts. This has a potential performance impact on
-          processes running early in the lifetime of the systemm until kswapd
-          finishes the initialisation.
+          by starting one-off "pgdatinitX" kernel thread for each node X. This
+          has a potential performance impact on processes running early in the
+          lifetime of the system until these kthreads finish the
+          initialisation.
 
 config IDLE_PAGE_TRACKING
         bool "Enable idle page tracking"