On 08/26/16 at 08:45am, "Zhou, Wenjian/周文剑" wrote:
> Hi Baoquan,
>
> Sorry, I misunderstood it before.
> Thanks for your detailed explanation.
>
> Hi Jon and Baoquan, I'm confused about how to adjust the kdump.txt.
> Does the patch set v9 still OK?
Yeah, I think it's OK. Let's wait for Jon's fee
On 08/25/16 at 01:10pm, Jonathan Corbet wrote:
> On Wed, 24 Aug 2016 13:06:45 +0800
> Baoquan He wrote:
>
> > Hi Jon, do you think change as below is OK to you?
>
> So nr_cpus is the maximum value, and maxcpus is the current number.
> Figures. No wonder the documentation is confusing...
Yes. T
Hi Baoquan,
Sorry, I misunderstood it before.
Thanks for your detailed explanation.
Hi Jon and Baoquan, I'm confused about how to adjust the kdump.txt.
Does the patch set v9 still OK?
--
Thanks
Zhou
On 08/24/2016 01:06 PM, Baoquan He wrote:
On 08/22/16 at 09:14am, "Zhou, Wenjian/周文剑" wrote:
On Wed, 24 Aug 2016 13:06:45 +0800
Baoquan He wrote:
> Hi Jon, do you think change as below is OK to you?
So nr_cpus is the maximum value, and maxcpus is the current number.
Figures. No wonder the documentation is confusing...
Anyway, this is much more along the lines of what I was hoping for,
On 08/22/16 at 09:14am, "Zhou, Wenjian/周文剑" wrote:
> On 08/19/2016 11:57 PM, Jonathan Corbet wrote:
> >On Fri, 19 Aug 2016 08:33:21 +0800
> >"Zhou, Wenjian/周文剑" wrote:
> >
> >>I was also confused by maxcpus and nr_cpus before writing this patch.
> >>I think it is a good choice to describe it in ke
On 08/19/2016 11:57 PM, Jonathan Corbet wrote:
On Fri, 19 Aug 2016 08:33:21 +0800
"Zhou, Wenjian/周文剑" wrote:
I was also confused by maxcpus and nr_cpus before writing this patch.
I think it is a good choice to describe it in kernel-parameters.txt.
Then, only two things need to be done I think
On Fri, 19 Aug 2016 08:33:21 +0800
"Zhou, Wenjian/周文剑" wrote:
> I was also confused by maxcpus and nr_cpus before writing this patch.
> I think it is a good choice to describe it in kernel-parameters.txt.
>
> Then, only two things need to be done I think.
> One is move the above description to m
On Thu, 18 Aug 2016 11:11:46 +0800
Zhou Wenjian wrote:
Thank you for working to improve the documentation!
> * We generally don' have to bring up a 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 wh
Hi Jonathan,
Thanks for your reply.
On 08/19/2016 01:18 AM, Jonathan Corbet wrote:
On Thu, 18 Aug 2016 11:11:46 +0800
Zhou Wenjian wrote:
Thank you for working to improve the documentation!
* We generally don' have to bring up a SMP kernel just to capture the
dump. Hence generally it
nr_cpus can help to save memory. So we should remind user of it.
Signed-off-by: Zhou Wenjian
Acked-by: Baoquan He
Acked-by: Xunlei Pang
---
Documentation/kdump/kdump.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 88
10 matches
Mail list logo
