From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753056AbcHBJGi (ORCPT ); Tue, 2 Aug 2016 05:06:38 -0400 Received: from cn.fujitsu.com ([59.151.112.132]:40718 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752187AbcHBJE5 (ORCPT ); Tue, 2 Aug 2016 05:04:57 -0400 X-IronPort-AV: E=Sophos;i="5.22,518,1449504000"; d="scan'208";a="9422692" Message-ID: <57A05E7D.90101@cn.fujitsu.com> Date: Tue, 2 Aug 2016 16:49:01 +0800 From: =?UTF-8?B?Ilpob3UsIFdlbmppYW4v5ZGo5paH5YmRIg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Baoquan He CC: , , , Subject: Re: [PATCH v2] Documentation: kdump: add description of bringing up SMP dump-capture kernel References: <1470010988-18050-1-git-send-email-zhouwj-fnst@cn.fujitsu.com> <20160802074602.GA3663@x1.redhat.com> In-Reply-To: <20160802074602.GA3663@x1.redhat.com> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-yoursite-MailScanner-ID: A486B42CA553.AA7CA X-yoursite-MailScanner: Found to be clean X-yoursite-MailScanner-From: zhouwj-fnst@cn.fujitsu.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Baoquan, On 08/02/2016 03:46 PM, Baoquan He wrote: > Hi Wenjian, > > On 08/01/16 at 08:23am, Zhou Wenjian wrote: >> v1->v2: change nr_cpus to maxcpus >> >> SMP dump-capture kernel is useful to improve the performance of kdump in >> some cases. So add the description of bringing up SMP dump-capture kernel. >> >> Signed-off-by: Zhou Wenjian > > Discussed with people, it could be better to adjust the > description about nr_cpus and maxcpus part. I think you can still > describe nr_cpus/maxcpus in patch 1/2, and keep parallel dumping part in > 2/2. > > Originally maxcpus=1 is used for all ARCHes. Later people found > nr_cpus=1 is better since nr_cpus decides the number of possible cpu > while maxcpus decides the max working cpu after system boot. So nr_cpus > can save memory because percpu will pre-allocate memory for each > possible cpu for hotplug. So on x86 nr_cpus is used because much memory > can be saved if possible cpu number is very large. > > So you can mention that both maxcpus and nr_cpus can be used but nr_cpus > has advantage if it has been implemented in some ARCHes like x86_64. And > I guess you mush have tested parallel dumping feature with nr_cpus > specified, it makes sense to tell people with the real situation. > I think it is better to describe the difference in somewhere else. Maybe, it's a good choice which just replace maxcpus by maxcpus/nr_cpus. Then user can choose maxcpus or nr_cpus. What do you think about it? -- Thanks Zhou > Thanks > Baoquan > >> --- >> Documentation/kdump/kdump.txt | 6 ++++++ >> 1 file changed, 6 insertions(+) >> >> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt >> index 88ff63d..c5762b7 100644 >> --- a/Documentation/kdump/kdump.txt >> +++ b/Documentation/kdump/kdump.txt >> @@ -394,6 +394,12 @@ Notes on loading the dump-capture kernel: >> dump. Hence generally it is useful either to build a UP dump-capture >> kernel or specify maxcpus=1 option while loading dump-capture kernel. >> >> +* We should bring up a SMP dump-capture kernel if we intend to use multi-threads >> + programs with it, such as parallel dump feature of makedumpfile. Otherwise, >> + the multi-threads program may have a great performance degradation. >> + To bring up a SMP dump-capture kernel, we should specify maxcpus=[X] and >> + disable_cpu_apic=[Y] options while loading it. >> + >> * 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 >> is done on all other architectures. If no elfcorehdr= kernel parameter is >> -- >> 1.8.3.1 >> >> >> > >