From: Vlastimil Babka <vbabka@suse.cz>
To: Balbir Singh <bsingharora@gmail.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-mm@kvack.org, Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux--foundation.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] fadump: Disable deferred page struct initialisation
Date: Wed, 3 Aug 2016 08:07:19 +0200 [thread overview]
Message-ID: <acefe941-2c2a-d7d2-0720-4cfbee404a16@suse.cz> (raw)
In-Reply-To: <1470201642.5034.3.camel@gmail.com>
On 08/03/2016 07:20 AM, Balbir Singh wrote:
> On Tue, 2016-08-02 at 18:49 +0530, Srikar Dronamraju wrote:
>> Fadump kernel reserves significant number of memory blocks. On a multi-node
>> machine, with CONFIG_DEFFERRED_STRUCT_PAGE support, fadump kernel fails to
>> boot. Fix this by disabling deferred page struct initialisation.
>>
>
> How much memory does a fadump kernel need? Can we bump up the limits depending
> on the config. I presume when you say fadump kernel you mean kernel with
> FADUMP in the config?
>
> BTW, I would much rather prefer a config based solution that does not select
> DEFERRED_INIT if FADUMP is enabled.
IIRC the kdump/fadump kernel is typically the same vmlinux as the main
kernel, just with special initrd and boot params. So if you want
deferred init for the main kernel, this would be impractical.
> Balbir
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-08-03 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 13:19 [PATCH 0/0] Disable deferred struct page initialisation on Fadump Srikar Dronamraju
2016-08-02 13:19 ` [PATCH 1/2] mm: Allow disabling deferred struct page initialisation Srikar Dronamraju
2016-08-02 18:09 ` Dave Hansen
2016-08-03 6:38 ` Srikar Dronamraju
2016-08-03 18:17 ` Dave Hansen
2016-08-04 5:25 ` Srikar Dronamraju
2016-08-02 13:19 ` [PATCH 2/2] fadump: Disable deferred page struct initialisation Srikar Dronamraju
2016-08-03 5:20 ` Balbir Singh
2016-08-03 6:07 ` Vlastimil Babka [this message]
2016-08-03 11:34 ` Michael Ellerman
2016-08-03 6:35 ` Srikar Dronamraju
2016-08-03 19:40 ` Dave Hansen
2016-08-04 5:10 ` Srikar Dronamraju
2016-08-04 10:28 ` Mel Gorman
2016-08-04 13:54 ` Srikar Dronamraju
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=acefe941-2c2a-d7d2-0720-4cfbee404a16@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux--foundation.org \
--cc=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=srikar@linux.vnet.ibm.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