mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-19 11:07:39 +07:00
800c02f5d0
The nommu-mmap.txt file provides description of user visible behaviuour. So, move it to the admin-guide. As it is already at the ReST, also rename it. Suggested-by: Mike Rapoport <rppt@linux.ibm.com> Suggested-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Link: https://lore.kernel.org/r/3a63d1833b513700755c85bf3bda0a6c4ab56986.1592918949.git.mchehab+huawei@kernel.org Signed-off-by: Jonathan Corbet <corbet@lwn.net>
41 lines
1.2 KiB
ReStructuredText
41 lines
1.2 KiB
ReStructuredText
=================
|
|
Memory Management
|
|
=================
|
|
|
|
Linux memory management subsystem is responsible, as the name implies,
|
|
for managing the memory in the system. This includes implemnetation of
|
|
virtual memory and demand paging, memory allocation both for kernel
|
|
internal structures and user space programms, mapping of files into
|
|
processes address space and many other cool things.
|
|
|
|
Linux memory management is a complex system with many configurable
|
|
settings. Most of these settings are available via ``/proc``
|
|
filesystem and can be quired and adjusted using ``sysctl``. These APIs
|
|
are described in Documentation/admin-guide/sysctl/vm.rst and in `man 5 proc`_.
|
|
|
|
.. _man 5 proc: http://man7.org/linux/man-pages/man5/proc.5.html
|
|
|
|
Linux memory management has its own jargon and if you are not yet
|
|
familiar with it, consider reading
|
|
:ref:`Documentation/admin-guide/mm/concepts.rst <mm_concepts>`.
|
|
|
|
Here we document in detail how to interact with various mechanisms in
|
|
the Linux memory management.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
concepts
|
|
cma_debugfs
|
|
hugetlbpage
|
|
idle_page_tracking
|
|
ksm
|
|
memory-hotplug
|
|
nommu-map
|
|
numa_memory_policy
|
|
numaperf
|
|
pagemap
|
|
soft-dirty
|
|
transhuge
|
|
userfaultfd
|