From: Dave Hansen <dave.hansen@intel.com>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Balbir Singh <bsingharora@gmail.com>
Cc: linux-mm@kvack.org, Mel Gorman <mgorman@techsingularity.net>,
Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Ellerman <mpe@ellerman.id.au>,
mahesh@linux.vnet.ibm.com
Subject: Re: [PATCH 2/2] fadump: Disable deferred page struct initialisation
Date: Wed, 3 Aug 2016 12:40:17 -0700 [thread overview]
Message-ID: <57A248A1.40807@intel.com> (raw)
In-Reply-To: <20160803063538.GH6310@linux.vnet.ibm.com>
On 08/02/2016 11:35 PM, Srikar Dronamraju wrote:
> On a regular kernel with CONFIG_FADUMP and fadump configured, 5% of the
> total memory is reserved for booting the kernel on crash. On crash,
> fadump kernel reserves the 95% memory and boots into the 5% memory that
> was reserved for it. It then parses the reserved 95% memory to collect
> the dump.
>
> The problem is not about the amount of memory thats reserved for fadump
> kernel. Even if we increase/decrease, we will still end up with the same
> issue.
Oh, and the dentry/inode caches are sized based on 100% of memory, not
the 5% that's left after the fadump reservation?
Is the deferred initialization kicked in progress at the time we do the
dentry/inode allocations? Can waiting a bit let the allocation succeed?
--
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 19:40 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
2016-08-03 11:34 ` Michael Ellerman
2016-08-03 6:35 ` Srikar Dronamraju
2016-08-03 19:40 ` Dave Hansen [this message]
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=57A248A1.40807@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=srikar@linux.vnet.ibm.com \
--cc=vbabka@suse.cz \
/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