Re: [PATCH -v2 0/11] x86: memblock related cleanup

From: Yinghai Lu
Date: Tue Feb 15 2011 - 01:37:24 EST


On Mon, Feb 7, 2011 at 3:17 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> 1. allocate bootmem with memblock will follow top-down
> 2. make page table cold be as high and on local node.
> 3. seperate bootmem.c into nobootmem.c.
>
> [PATCH 01/11] memblock: Don't adjust size in memblock_find_base()
> [PATCH 02/11] x86, mm, 64bit: Put early page table high.
> [PATCH 03/11] x86, 64bit, gart: Fix allocation with memblock
> [PATCH 04/11] memblock: Make find_memory_core_early() find from top-down
> [PATCH 05/11] x86: Change get_max_mapped() to inline
> [PATCH 06/11] x86, 64bit, numa: Allocate memnodemap under max_pfn_mapped
> [PATCH 07/11] x86, 64bit, numa: Put pgtable to local node memory
> [PATCH 08/11] x86: Rename e820_table_* to pgt_buf_*
> [PATCH 09/11] bootmem: Add nobootmem.c to reduce the #ifdef
> [PATCH 10/11] mm: Move contig_page_data define to bootmem.c/nobootmem.c
> [PATCH 11/11] memblock: Move __alloc_memory_core_early() to nobootmem.c
>
> First patch is already in -mm, but better to go with this patchset as patch 3 need that.
> and patch 4 is depending patch 3.
>

Ingo,

patch1 is in mainline already via Andrew path.
patch2 to patch7 are in tip/x86/bootmem, and now it is in tip/master.

please check
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-2.6-yinghai.git
memblock

for last four patches.
main change is creating nobootmem.c for memblock bootmem wrapper.


arch/x86/include/asm/init.h | 6 +-
arch/x86/mm/init.c | 20 +-
arch/x86/mm/init_32.c | 8 +-
arch/x86/mm/init_64.c | 4 +-
arch/x86/xen/mmu.c | 2 +-
include/linux/mm.h | 2 -
mm/Makefile | 8 +-
mm/bootmem.c | 180 +-----------------
mm/nobootmem.c | 435 +++++++++++++++++++++++++++++++++++++++++++
mm/page_alloc.c | 37 ----
10 files changed, 472 insertions(+), 230 deletions(-)
create mode 100644 mm/nobootmem.c


Thanks

Yinghai Lu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/