lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1310460395-30913-1-git-send-email-tj@kernel.org>
Date:	Tue, 12 Jul 2011 10:46:27 +0200
From:	Tejun Heo <tj@...nel.org>
To:	mingo@...hat.com, hpa@...or.com, tglx@...utronix.de,
	benh@...nel.crashing.org, yinghai@...nel.org, davem@...emloft.net
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	x86@...nel.org
Subject: [PATCHSET x86/mm] memblock, x86: Implement for_each_mem_pfn_range() and use it to improve memblock allocator

Hello,

Currently, page_alloc internal functions walk early_node_map[]
directly while external users can walk it with callback based
work_with_active_regions().

Callback based walking is awkward to use and iterating
early_node_map[] directly hinders scheduled move of node information
to memblock.  This patchset implements for_each_mem_pfn_range() which
is easier for and used by both internal and external users, and
provides indirection layer so that node memory information can be
moved elsewhere.

This patchset is composed of two parts.  The first half implements the
new iterator and converts all internal and external users other than
the ones which directly manipulate early_node_map[].

The second half uses the new iterator to improve memblock_nid_range(),
implement proper top-down memblock allocation and replaces x86
specific memblock allocator with it.

Most of the changes are in mm/page_alloc,memblock.c and under x86 but
there are small updates to sparc and powerpc.  They shouldn't change
any behavior but I've only compile tested them.

 0001-bootmem-Replace-work_with_active_regions-with-for_ea.patch
 0002-bootmem-Reimplement-__absent_pages_in_range-using-fo.patch
 0003-bootmem-Use-for_each_mem_pfn_range-in-page_alloc.c.patch
 0004-memblock-Improve-generic-memblock_nid_range-using-fo.patch
 0005-memblock-Don-t-allow-archs-to-override-memblock_nid_.patch
 0006-memblock-Make-memblock_alloc_-try_-nid-top-down.patch
 0007-memblock-Separate-out-memblock_find_in_range_node.patch
 0008-memblock-x86-Replace-memblock_x86_find_in_range_node.patch

0001 implements for_each_mem_pfn_range() and replaces
work_with_active_regions() with it.

0002-0003 apply for_each_mem_pfn_range() in page_alloc.c.

0004-0008 implement proper top-down allocation for memblock and
replace x86 specific memblock allocator with it.

This patchset is on top of

  x86/urgent (5da0ef9a85 "x86: Disable AMD_NUMA for 32bit for now")
+ pfn->nid granularity check patches [1]
+ "memblock, x86: Misc cleanups" patchset [2]

and available in the following git branch.

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-x86-mm-iter

This patchset simplifies early_node_map[] walking and removes
duplicate x86 specific implementation and removes just shy of 200
lines.

 arch/powerpc/mm/numa.c          |   50 +-----
 arch/sparc/mm/init_64.c         |    4
 arch/x86/include/asm/memblock.h |    1
 arch/x86/mm/memblock.c          |   38 ----
 arch/x86/mm/numa.c              |    9 -
 drivers/pci/intel-iommu.c       |   24 +-
 include/linux/memblock.h        |    5
 include/linux/mm.h              |   24 ++
 mm/memblock.c                   |   90 ++++-------
 mm/nobootmem.c                  |    3
 mm/page_alloc.c                 |  326 +++++++++++-----------------------------
 11 files changed, 190 insertions(+), 384 deletions(-)

Thanks.

--
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/1166521
[2] http://thread.gmane.org/gmane.linux.kernel.cross-arch/10338
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ