From: Baoquan He <bhe@redhat.com>
To: corbet@lwn.net, akpm@linux-foundation.org
Cc: linux-doc@vger.kernel.org, kexec@lists.infradead.org,
Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>,
xlpang@redhat.com, linux-kernel@vger.kernel.org,
dyoung@redhat.com
Subject: Re: [PATCH v10 3/3] Documentation: kdump: add description of enable multi-cpus support
Date: Mon, 19 Sep 2016 13:52:57 +0800 [thread overview]
Message-ID: <20160919055257.GA8693@x1.redhat.com> (raw)
In-Reply-To: <1474257665-8838-4-git-send-email-bhe@redhat.com>
On 09/19/16 at 12:01pm, Baoquan He wrote:
> From: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>
>
> Multi-cpu support is useful to improve the performance of kdump in
> some cases. So add the description of enable multi-cpu support in
> dump-capture kernel.
>
> Signed-off-by: Zhou Wenjian <zhouwj-fnst@cn.fujitsu.com>
> Acked-by: Baoquan He <bhe@redhat.com>
> Acked-by: Xunlei Pang <xpang@redhat.com>
> Signed-off-by: Baoquan He <bhe@redhat.com>
Oh, sorry. My git config caused this Signed-off-by adding automatically.
Will resend. Nack this patchset.
> ---
> Documentation/kdump/kdump.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
> index f7ef340..b0eb27b 100644
> --- a/Documentation/kdump/kdump.txt
> +++ b/Documentation/kdump/kdump.txt
> @@ -396,6 +396,13 @@ Notes on loading the dump-capture kernel:
> Note, though maxcpus always works, you had better replace it with
> nr_cpus to save memory if supported by the current ARCH, such as x86.
>
> +* You should enable multi-cpu support in dump-capture kernel if you intend
> + to use multi-thread programs with it, such as parallel dump feature of
> + makedumpfile. Otherwise, the multi-thread program may have a great
> + performance degradation. To enable multi-cpu support, you should bring up an
> + SMP dump-capture kernel and specify maxcpus/nr_cpus, disable_cpu_apicid=[X]
> + 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
> --
> 2.5.5
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-09-19 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 4:01 [PATCH v10 0/3] Documentation: add description of enable multi-cpus support for kdump Baoquan He
2016-09-19 4:01 ` [PATCH v10 1/3] docs: kernel-parameter : Improve the description of nr_cpus and maxcpus Baoquan He
2016-09-19 4:01 ` [PATCH v10 2/3] Documentation: kdump: remind user of nr_cpus Baoquan He
2016-09-19 4:01 ` [PATCH v10 3/3] Documentation: kdump: add description of enable multi-cpus support Baoquan He
2016-09-19 5:52 ` Baoquan He [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160919055257.GA8693@x1.redhat.com \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xlpang@redhat.com \
--cc=zhouwj-fnst@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).