From: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, qiuxishi@huawei.com, dhowells@redhat.com,
daeseok.youn@gmail.com, liuj97@gmail.com, yinghai@kernel.org,
phacht@linux.vnet.ibm.com, zhangyanfei@cn.fujitsu.com,
santosh.shilimkar@ti.com, grygorii.strashko@ti.com,
tangchen@cn.fujitsu.com
Subject: [PATCH V2 0/2] mm/memblock: Excluded memory, free_all_bootmem
Date: Mon, 13 Jan 2014 13:48:59 +0100 [thread overview]
Message-ID: <1389617341-568-1-git-send-email-phacht@linux.vnet.ibm.com> (raw)
These two patches fit (only) on top of linux-next!
The first patch changes back the behavior of free_all_bootmem() to
a more generic way: With CONFIG_DISCARD_MEMBLOCK memblock.memory
and memblock.reserved will be freed (if allocated, of course).
Removed the debugfs dependency. Think this is cleaner.
While further working on the s390 migration to memblock it is desirable
to have memblock support unmapped (i.e. completely forgotten and unused)
memory areas. The usual way of just forgetting about them by means of
truncating the memblocks does not work for us because we still need the
information about the real full memory structure at a later time.
Philipp Hachtmann (2):
mm/nobootmem: free_all_bootmem again
mm/memblock: Add support for excluded memory areas
include/linux/memblock.h | 50 +++++++--
mm/Kconfig | 3 +
mm/memblock.c | 276 ++++++++++++++++++++++++++++++++++-------------
mm/nobootmem.c | 13 ++-
4 files changed, 255 insertions(+), 87 deletions(-)
--
1.8.4.5
--
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 reply other threads:[~2014-01-13 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 12:48 Philipp Hachtmann [this message]
2014-01-13 12:49 ` [PATCH V2 1/2] mm/nobootmem: free_all_bootmem again Philipp Hachtmann
2014-01-13 12:49 ` [PATCH V2 2/2] mm/memblock: Add support for excluded memory areas Philipp Hachtmann
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=1389617341-568-1-git-send-email-phacht@linux.vnet.ibm.com \
--to=phacht@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=daeseok.youn@gmail.com \
--cc=dhowells@redhat.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=qiuxishi@huawei.com \
--cc=santosh.shilimkar@ti.com \
--cc=tangchen@cn.fujitsu.com \
--cc=yinghai@kernel.org \
--cc=zhangyanfei@cn.fujitsu.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