mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-12-28 13:34:38 +08:00
530d4c0cfd
Link: http://lkml.kernel.org/r/1536927045-23536-31-git-send-email-rppt@linux.vnet.ibm.com Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Chris Zankel <chris@zankel.net> Cc: "David S. Miller" <davem@davemloft.net> Cc: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Greentime Hu <green.hu@gmail.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: Guan Xuetao <gxt@pku.edu.cn> Cc: Ingo Molnar <mingo@redhat.com> Cc: "James E.J. Bottomley" <jejb@parisc-linux.org> Cc: Jonas Bonn <jonas@southpole.se> Cc: Jonathan Corbet <corbet@lwn.net> Cc: Ley Foon Tan <lftan@altera.com> Cc: Mark Salter <msalter@redhat.com> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com> Cc: Matt Turner <mattst88@gmail.com> Cc: Michael Ellerman <mpe@ellerman.id.au> Cc: Michal Hocko <mhocko@suse.com> Cc: Michal Simek <monstr@monstr.eu> Cc: Palmer Dabbelt <palmer@sifive.com> Cc: Paul Burton <paul.burton@mips.com> Cc: Richard Kuo <rkuo@codeaurora.org> Cc: Richard Weinberger <richard@nod.at> Cc: Rich Felker <dalias@libc.org> Cc: Russell King <linux@armlinux.org.uk> Cc: Serge Semin <fancer.lancer@gmail.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Tony Luck <tony.luck@intel.com> Cc: Vineet Gupta <vgupta@synopsys.com> Cc: Yoshinori Sato <ysato@users.sourceforge.jp> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
42 lines
1.4 KiB
ReStructuredText
42 lines
1.4 KiB
ReStructuredText
===========================
|
|
Boot time memory management
|
|
===========================
|
|
|
|
Early system initialization cannot use "normal" memory management
|
|
simply because it is not set up yet. But there is still need to
|
|
allocate memory for various data structures, for instance for the
|
|
physical page allocator.
|
|
|
|
A specialized allocator called ``memblock`` performs the
|
|
boot time memory management. The architecture specific initialization
|
|
must set it up in :c:func:`setup_arch` and tear it down in
|
|
:c:func:`mem_init` functions.
|
|
|
|
Once the early memory management is available it offers a variety of
|
|
functions and macros for memory allocations. The allocation request
|
|
may be directed to the first (and probably the only) node or to a
|
|
particular node in a NUMA system. There are API variants that panic
|
|
when an allocation fails and those that don't.
|
|
|
|
Memblock also offers a variety of APIs that control its own behaviour.
|
|
|
|
Memblock Overview
|
|
=================
|
|
|
|
.. kernel-doc:: mm/memblock.c
|
|
:doc: memblock overview
|
|
|
|
|
|
Functions and structures
|
|
========================
|
|
|
|
Here is the description of memblock data structures, functions and
|
|
macros. Some of them are actually internal, but since they are
|
|
documented it would be silly to omit them. Besides, reading the
|
|
descriptions for the internal functions can help to understand what
|
|
really happens under the hood.
|
|
|
|
.. kernel-doc:: include/linux/memblock.h
|
|
.. kernel-doc:: mm/memblock.c
|
|
:functions:
|