LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Joerg Roedel <jroedel@suse.de>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high
Date: Fri, 13 Feb 2015 23:34:38 +0800 [thread overview]
Message-ID: <20150213153438.GA4483@dhcp-17-102.nay.redhat.com> (raw)
In-Reply-To: <20150209122042.GA29106@8bytes.org>
On 02/09/15 at 01:20pm, Joerg Roedel wrote:
> Hi Baoquan,
>
> On Wed, Feb 04, 2015 at 03:10:20PM +0100, Joerg Roedel wrote:
> > That makes sense. I also asked the customer to test intermediate values,
> > we already know that it works with 256MB but also that 128MB are not
> > enough. I will report back when I have the results of the intermediate
> > values in 32MB steps.
>
> I got the results from the customer, and it turns out that a value of
> 192MB is sufficient to make the kdump succeed. It fails with 128MB and
> 160MB.
>
> So I think we can settle in 192MB for now. What do you think?
Hi Joerg,
Sorry for late reply.
So that machine need eat memory between 160M and 192M. Then how about
setting it as 256M? Since 192M seems very close to the brink, and
setting it larger can keep enough space to extend for increasing dma
device on larger machines, otherwise this value could be increased soon.
Wasting some low memory is better than kdump kernel can't bootup
caused by not enough low memory. If someone grudge the low mem they can
specify crashkernel=size,low manually.
Conclusively, I like 256M since the testing data showed it's sufficient
now and should be save for a long time.
Thanks
Baoquan
next prev parent reply other threads:[~2015-02-13 15:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 14:51 [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-06 14:51 ` [PATCH 1/3] swiotlb: Warn on allocation failure in swiotlb_alloc_coherent Joerg Roedel
2015-01-23 17:04 ` Borislav Petkov
2015-01-26 11:49 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 2/3] x86, swiotlb: Try coherent allocations with __GFP_NOWARN Joerg Roedel
2015-01-23 17:03 ` Borislav Petkov
2015-01-26 3:22 ` Baoquan He
2015-01-26 11:54 ` Joerg Roedel
2015-01-06 14:51 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2015-01-23 8:44 ` Baoquan He
2015-01-26 12:07 ` Joerg Roedel
2015-02-01 8:41 ` Baoquan He
2015-02-04 14:10 ` Joerg Roedel
2015-02-09 12:20 ` Joerg Roedel
2015-02-13 15:34 ` Baoquan He [this message]
2015-02-13 22:28 ` Joerg Roedel
2015-02-14 11:44 ` Baoquan He
2015-01-23 17:02 ` Borislav Petkov
2015-01-26 12:11 ` Joerg Roedel
2015-01-26 12:20 ` Borislav Petkov
2015-01-26 12:40 ` Joerg Roedel
2015-01-26 12:45 ` Borislav Petkov
2015-01-14 13:35 ` [PATCH 0/3 v2] Fix kdump failures with crashkernel=high Joerg Roedel
2015-01-19 19:26 ` Borislav Petkov
2015-02-14 10:58 ` Baoquan He
2015-02-14 16:11 ` Joerg Roedel
2015-06-02 8:54 ` Baoquan He
2015-06-02 9:08 ` Joerg Roedel
-- strict thread matches above, loose matches on Subject: below --
2015-06-05 10:29 [PATCH 0/3 v3] " Joerg Roedel
2015-06-05 10:30 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
2014-11-28 11:29 [PATCH 0/3] Fix kdump failures with crashkernel=high Joerg Roedel
2014-11-28 11:29 ` [PATCH 3/3] x86, crash: Allocate enough low-mem when crashkernel=high Joerg Roedel
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=20150213153438.GA4483@dhcp-17-102.nay.redhat.com \
--to=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).