From: ebiederm@xmission.com (Eric W. Biederman)
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com,
linux-ia64@vger.kernel.org, linux-mm@kvack.org,
Neil Horman <nhorman@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, bernhard.walle@gmx.de,
Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [Patch 8/8] kexec: allow to shrink reserved memory
Date: Fri, 14 Aug 2009 15:17:34 -0700 [thread overview]
Message-ID: <m1tz0avy4h.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <4A83CD84.8040609@redhat.com> (Amerigo Wang's message of "Thu\, 13 Aug 2009 16\:23\:32 +0800")
Amerigo Wang <amwang@redhat.com> writes:
> Not that simple, marking it as "__init" means it uses some "__init" data which
> will be dropped after initialization.
If we start with the assumption that we will be reserving to much and
will free the memory once we know how much we really need I see a very
simple way to go about this. We ensure that the reservation of crash
kernel memory is done through a normal allocation so that we have
struct page entries for every page. On 32bit x86 that is an extra 1MB
for a 128MB allocation.
Then when it comes time to release that memory we clear whatever magic
flags we have on the page (like PG_reserve) and call free_page.
Eric
--
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:[~2009-08-14 22:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090812081731.5757.25254.sendpatchset@localhost.localdomain>
[not found] ` <20090812081906.5757.39417.sendpatchset@localhost.localdomain>
[not found] ` <m1bpmk8l1g.fsf@fess.ebiederm.org>
2009-08-13 3:32 ` Amerigo Wang
2009-08-13 6:18 ` Eric W. Biederman
2009-08-13 8:23 ` Amerigo Wang
2009-08-14 22:17 ` Eric W. Biederman [this message]
2009-08-17 9:50 ` Amerigo Wang
2009-08-18 0:29 ` KAMEZAWA Hiroyuki
2009-08-18 6:31 ` Amerigo Wang
2009-08-18 8:25 ` KAMEZAWA Hiroyuki
2009-08-18 8:51 ` Amerigo Wang
2009-08-18 10:35 ` Amerigo Wang
2009-08-18 23:57 ` KAMEZAWA Hiroyuki
2009-08-19 2:41 ` Amerigo Wang
2009-08-19 8:13 ` KAMEZAWA Hiroyuki
2009-08-19 10:47 ` Amerigo Wang
2009-08-20 9:15 ` Amerigo Wang
2009-08-21 0:34 ` KAMEZAWA Hiroyuki
2009-08-21 1:59 ` Amerigo Wang
2009-08-21 2:03 ` KAMEZAWA Hiroyuki
2009-08-21 2:47 ` Amerigo Wang
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=m1tz0avy4h.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=andi@firstfloor.org \
--cc=avorontsov@ru.mvista.com \
--cc=bernhard.walle@gmx.de \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nhorman@redhat.com \
--cc=tony.luck@intel.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