[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1471487495-22787-2-git-send-email-zhouwj-fnst@cn.fujitsu.com>
Date: Thu, 18 Aug 2016 10:31:34 +0800
From: Zhou Wenjian <zhouwj-fnst@...fujitsu.com>
To: <linux-kernel@...r.kernel.org>
CC: <akpm@...ux-foundation.org>, <dyoung@...hat.com>, <bhe@...hat.com>,
<vgoyal@...hat.com>, <corbet@....net>, <kexec@...ts.infradead.org>,
<linux-doc@...r.kernel.org>, <xlpang@...hat.com>
Subject: [PATCH v8 1/2] Documentation: kdump: remind user of nr_cpus
nr_cpus can help to save memory. So we should remind user of it.
Signed-off-by: Zhou Wenjian <zhouwj-fnst@...fujitsu.com>
Acked-by: Baoquan He <bhe@...hat.com>
Acked-by: Xunlei Pang <xpang@...hat.com>
---
Documentation/kdump/kdump.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 88ff63d..e8da1d5 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -390,9 +390,11 @@ Notes on loading the dump-capture kernel:
* Boot parameter "1" boots the dump-capture kernel into single-user
mode without networking. If you want networking, use "3".
-* We generally don' have to bring up a SMP kernel just to capture the
+* We generally don' have to bring up an SMP kernel just to capture the
dump. Hence generally it is useful either to build a UP dump-capture
kernel or specify maxcpus=1 option while loading dump-capture kernel.
+ Note, though maxcpus always works, you should replace it by nr_cpus to
+ save memory if supported by the current ARCH, such as x86.
* For s390x there are two kdump modes: If a ELF header is specified with
the elfcorehdr= kernel parameter, it is used by the kdump kernel as it
--
1.8.3.1
Powered by blists - more mailing lists