[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1389617341-568-1-git-send-email-phacht@linux.vnet.ibm.com>
Date: Mon, 13 Jan 2014 13:48:59 +0100
From: Philipp Hachtmann <phacht@...ux.vnet.ibm.com>
To: akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, qiuxishi@...wei.com, dhowells@...hat.com,
daeseok.youn@...il.com, liuj97@...il.com, yinghai@...nel.org,
phacht@...ux.vnet.ibm.com, zhangyanfei@...fujitsu.com,
santosh.shilimkar@...com, grygorii.strashko@...com,
tangchen@...fujitsu.com
Subject: [PATCH V2 0/2] mm/memblock: Excluded memory, free_all_bootmem
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists