From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
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>,
linuxppc-dev@lists.ozlabs.org,
Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
Hari Bathini <hbathini@linux.vnet.ibm.com>,
Dave Hansen <dave.hansen@intel.com>,
Balbir Singh <bsingharora@gmail.com>
Subject: Re: [PATCH] fadump: Register the memory reserved by fadump
Date: Fri, 5 Aug 2016 12:58:38 +0530 [thread overview]
Message-ID: <20160805072838.GF11268@linux.vnet.ibm.com> (raw)
In-Reply-To: <87mvkritii.fsf@concordia.ellerman.id.au>
* Michael Ellerman <mpe@ellerman.id.au> [2016-08-05 17:07:01]:
> Srikar Dronamraju <srikar@linux.vnet.ibm.com> writes:
>
> > Fadump kernel reserves large chunks of memory even before the pages are
> > initialized. This could mean memory that corresponds to several nodes might
> > fall in memblock reserved regions.
> >
> ...
> > Register the memory reserved by fadump, so that the cache sizes are
> > calculated based on the free memory (i.e Total memory - reserved
> > memory).
>
> The memory is reserved, with memblock_reserve(). Why is that not sufficient?
>
> cheers
>
Because at page initialization time, the kernel doesnt know how many
pages are reserved. One way to do that would be to walk through the
different memory reserved blocks and calculate the size. But Mel feels
thats an overhead (from his reply to the other thread) esp for just one
use case.
--
Thanks and Regards
Srikar Dronamraju
--
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-05 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 13:42 [PATCH] fadump: Register the memory reserved by fadump Srikar Dronamraju
2016-08-04 14:09 ` Mel Gorman
2016-08-04 15:27 ` Srikar Dronamraju
2016-08-05 7:07 ` Michael Ellerman
2016-08-05 7:28 ` Srikar Dronamraju [this message]
2016-08-05 9:25 ` Michael Ellerman
2016-08-05 10:06 ` Mel Gorman
2016-08-10 6:02 ` Michael Ellerman
2016-08-10 6:40 ` Srikar Dronamraju
2016-08-10 6:57 ` Michael Ellerman
2016-08-10 9:21 ` Srikar Dronamraju
2016-08-10 7:51 ` Mel Gorman
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=20160805072838.GF11268@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=dave.hansen@intel.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).