| /linux-6.15/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 2 Memory Hot(Un)Plug
5 This document describes generic Linux support for memory hot(un)plug with
13 Memory hot(un)plug allows for increasing and decreasing the size of physical
14 memory available to a machine at runtime. In the simplest case, it consists of
18 Memory hot(un)plug is used for various purposes:
20 - The physical memory available to a machine can be adjusted at runtime, up- or
21 downgrading the memory capacity. This dynamic memory resizing, sometimes
26 example is replacing failing memory modules.
28 - Reducing energy consumption either by physically unplugging memory modules or
29 by logically unplugging (parts of) memory modules from Linux.
[all …]
|
| D | concepts.rst | 5 The memory management in Linux is a complex system that evolved over the
7 systems from MMU-less microcontrollers to supercomputers. The memory
16 Virtual Memory Primer
19 The physical memory in a computer system is a limited resource and
20 even for systems that support memory hotplug there is a hard limit on
21 the amount of memory that can be installed. The physical memory is not
27 All this makes dealing directly with physical memory quite complex and
28 to avoid this complexity a concept of virtual memory was developed.
30 The virtual memory abstracts the details of physical memory from the
32 physical memory (demand paging) and provides a mechanism for the
[all …]
|
| D | numaperf.rst | 2 NUMA Memory Performance
8 Some platforms may have multiple types of memory attached to a compute
9 node. These disparate memory ranges may share some characteristics, such
13 A system supports such heterogeneous memory by grouping each memory type
15 characteristics. Some memory may share the same node as a CPU, and others
16 are provided as memory only nodes. While memory only nodes do not provide
19 nodes with local memory and a memory only node for each of compute node::
30 A "memory initiator" is a node containing one or more devices such as
31 CPUs or separate memory I/O devices that can initiate memory requests.
32 A "memory target" is a node containing one or more physical address
[all …]
|
| /linux-6.15/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | 25 if ! ls $SYSFS/devices/system/memory/memory* > /dev/null 2>&1; then
26 echo $msg memory hotplug is not supported >&2
30 if ! grep -q 1 $SYSFS/devices/system/memory/memory*/removable; then
31 echo $msg no hot-pluggable memory >&2
37 # list all hot-pluggable memory
43 for memory in $SYSFS/devices/system/memory/memory*; do
44 if grep -q 1 $memory/removable &&
45 grep -q $state $memory/state; then
46 echo ${memory##/*/memory}
63 grep -q online $SYSFS/devices/system/memory/memory$1/state
[all …]
|
| /linux-6.15/Documentation/admin-guide/cgroup-v1/ |
| D | memory.rst | 2 Memory Resource Controller
12 The Memory Resource Controller has generically been referred to as the
13 memory controller in this document. Do not confuse memory controller
14 used here with the memory controller that is used in hardware.
17 When we mention a cgroup (cgroupfs's directory) with memory controller,
18 we call it "memory cgroup". When you see git-log and source code, you'll
22 Benefits and Purpose of the memory controller
25 The memory controller isolates the memory behaviour of a group of tasks
27 uses of the memory controller. The memory controller can be used to
30 Memory-hungry applications can be isolated and limited to a smaller
[all …]
|
| /linux-6.15/Documentation/mm/ |
| D | memory-model.rst | 4 Physical Memory Model
7 Physical memory in a system may be addressed in different ways. The
8 simplest case is when the physical memory starts at address 0 and
13 different memory banks are attached to different CPUs.
15 Linux abstracts this diversity using one of the two memory models:
17 memory models it supports, what the default memory model is and
20 All the memory models track the status of physical page frames using
23 Regardless of the selected memory model, there exists one-to-one
27 Each memory model defines :c:func:`pfn_to_page` and :c:func:`page_to_pfn`
34 The simplest memory model is FLATMEM. This model is suitable for
[all …]
|
| D | hmm.rst | 2 Heterogeneous Memory Management (HMM)
5 Provide infrastructure and helpers to integrate non-conventional memory (device
6 memory like GPU on board memory) into regular kernel path, with the cornerstone
7 of this being specialized struct page for such memory (see sections 5 to 7 of
10 HMM also provides optional helpers for SVM (Share Virtual Memory), i.e.,
18 related to using device specific memory allocators. In the second section, I
22 fifth section deals with how device memory is represented inside the kernel.
28 Problems of using a device specific memory allocator
31 Devices with a large amount of on board memory (several gigabytes) like GPUs
32 have historically managed their memory through dedicated driver specific APIs.
[all …]
|
| D | numa.rst | 12 or more CPUs, local memory, and/or IO buses. For brevity and to
26 Coherent NUMA or ccNUMA systems. With ccNUMA systems, all memory is visible
30 Memory access time and effective memory bandwidth varies depending on how far
31 away the cell containing the CPU or IO bus making the memory access is from the
32 cell containing the target memory. For example, access to memory by CPUs
34 bandwidths than accesses to memory on other, remote cells. NUMA platforms
39 memory bandwidth. However, to achieve scalable memory bandwidth, system and
40 application software must arrange for a large majority of the memory references
41 [cache misses] to be to "local" memory--memory on the same cell, if any--or
42 to the closest cell with memory.
[all …]
|
| /linux-6.15/Documentation/ABI/testing/ |
| D | sysfs-devices-memory | 1 What: /sys/devices/system/memory
5 The /sys/devices/system/memory contains a snapshot of the
6 internal state of the kernel memory blocks. Files could be
9 Users: hotplug memory add/remove tools
12 What: /sys/devices/system/memory/memoryX/removable
16 The file /sys/devices/system/memory/memoryX/removable is a
17 legacy interface used to indicated whether a memory block is
19 "1" if and only if the kernel supports memory offlining.
20 Users: hotplug memory remove tools
24 What: /sys/devices/system/memory/memoryX/phys_device
[all …]
|
| D | sysfs-edac-memory-repair | 7 pertains to the memory media repair features control, such as
8 PPR (Post Package Repair), memory sparing etc, where <dev-name>
10 device driver for the memory repair features.
12 Post Package Repair is a maintenance operation requests the memory
13 device to perform a repair operation on its media. It is a memory
14 self-healing feature that fixes a failing memory location by
16 CXL memory device with DRAM components that support PPR features may
28 decoders have been configured), memory devices (e.g. CXL)
30 physical address map. As such, the memory to repair must be
40 (RO) Memory repair type. For eg. post package repair,
[all …]
|
| /linux-6.15/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | fsl,ddr.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/fsl/fsl,ddr.yaml#
7 title: Freescale DDR memory controller
15 pattern: "^memory-controller@[0-9a-f]+$"
21 - fsl,qoriq-memory-controller-v4.4
22 - fsl,qoriq-memory-controller-v4.5
23 - fsl,qoriq-memory-controller-v4.7
24 - fsl,qoriq-memory-controller-v5.0
25 - const: fsl,qoriq-memory-controller
27 - fsl,bsc9132-memory-controller
28 - fsl,mpc8536-memory-controller
[all …]
|
| /linux-6.15/Documentation/arch/arm64/ |
| D | kdump.rst | 2 crashkernel memory reservation on arm64
9 reserved memory is needed to pre-load the kdump kernel and boot such
12 That reserved memory for kdump is adapted to be able to minimally
19 Through the kernel parameters below, memory can be reserved accordingly
21 large chunk of memomy can be found. The low memory reservation needs to
22 be considered if the crashkernel is reserved from the high memory area.
28 Low memory and high memory
31 For kdump reservations, low memory is the memory area under a specific
34 vmcore dumping can be ignored. On arm64, the low memory upper bound is
37 whole system RAM is low memory. Outside of the low memory described
[all …]
|
| /linux-6.15/Documentation/edac/ |
| D | memory_repair.rst | 4 EDAC Memory Repair Control
20 Some memory devices support repair operations to address issues in their
21 memory media. Post Package Repair (PPR) and memory sparing are examples of
27 Post Package Repair is a maintenance operation which requests the memory
28 device to perform repair operation on its media. It is a memory self-healing
29 feature that fixes a failing memory location by replacing it with a spare row
32 For example, a CXL memory device with DRAM components that support PPR
42 The data may not be retained and memory requests may not be correctly
46 For example, for CXL memory devices, see CXL spec rev 3.1 [1]_ sections
50 Memory Sparing
[all …]
|
| /linux-6.15/tools/testing/selftests/cgroup/ |
| D | test_memcontrol.c | 29 * the memory controller.
37 /* Create two nested cgroups with the memory controller enabled */ in test_memcg_subtree_control()
46 if (cg_write(parent, "cgroup.subtree_control", "+memory")) in test_memcg_subtree_control()
52 if (cg_read_strstr(child, "cgroup.controllers", "memory")) in test_memcg_subtree_control()
55 /* Create two nested cgroups without enabling memory controller */ in test_memcg_subtree_control()
70 if (!cg_read_strstr(child2, "cgroup.controllers", "memory")) in test_memcg_subtree_control()
109 current = cg_read_long(cgroup, "memory.current"); in alloc_anon_50M_check()
116 anon = cg_read_key_long(cgroup, "memory.stat", "anon "); in alloc_anon_50M_check()
143 current = cg_read_long(cgroup, "memory.current"); in alloc_pagecache_50M_check()
147 file = cg_read_key_long(cgroup, "memory.stat", "file "); in alloc_pagecache_50M_check()
[all …]
|
| /linux-6.15/Documentation/core-api/ |
| D | memory-hotplug.rst | 4 Memory hotplug
7 Memory hotplug event notifier
12 There are six types of notification defined in ``include/linux/memory.h``:
15 Generated before new memory becomes available in order to be able to
16 prepare subsystems to handle memory. The page allocator is still unable
17 to allocate from the new memory.
23 Generated when memory has successfully brought online. The callback may
24 allocate pages from the new memory.
27 Generated to begin the process of offlining memory. Allocations are no
28 longer possible from the memory but some of the memory to be offlined
[all …]
|
| /linux-6.15/drivers/base/ |
| D | memory.c | 3 * Memory subsystem support
9 * a SPARSEMEM-memory-model system's physical memory in /sysfs.
19 #include <linux/memory.h>
29 #define MEMORY_CLASS_NAME "memory"
79 * Memory blocks are cached in a local radix tree to avoid
86 * Memory groups, indexed by memory group id (mgid).
119 /* Show the memory block ID, relative to the memory block size */
203 * they describe (they remain until the memory is unplugged), doing in memory_block_online()
204 * their initialization and accounting at memory onlining/offlining in memory_block_online()
206 * belong to the same zone as the memory they backed. in memory_block_online()
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-v3/ |
| D | memory.json | 4 …memory accesses issued by the CPU load store unit, where those accesses are issued due to load or …
8 …memory errors (ECC or parity) in protected CPUs RAMs. On the core, this event counts errors in the…
16 …memory accesses issued by the CPU due to load operations. The event counts any memory load access,…
20 …memory accesses issued by the CPU due to store operations. The event counts any memory store acces…
24 …"PublicDescription": "Counts the number of memory read and write accesses in a cycle that incurred…
28 …"PublicDescription": "Counts the number of memory read accesses in a cycle that incurred additiona…
32 …"PublicDescription": "Counts the number of memory write access in a cycle that incurred additional…
36 …cription": "Counts the number of memory read and write accesses counted by MEM_ACCESS that are tag…
40 …"PublicDescription": "Counts the number of memory read accesses in a cycle that are tag checked by…
44 …"PublicDescription": "Counts the number of memory write accesses in a cycle that is tag checked by…
[all …]
|
| /linux-6.15/include/linux/ |
| D | memory.h | 3 * include/linux/memory.h - generic memory definition
9 * Basic handling of the devices is done in drivers/base/memory.c
12 * Memory block are exported via sysfs in the class/memory/devices/
26 * struct memory_group - a logical group of memory blocks
27 * @nid: The node id for all memory blocks inside the memory group.
28 * @memory_blocks: List of all memory blocks belonging to this memory group.
29 * @present_kernel_pages: Present (online) memory outside ZONE_MOVABLE of this
30 * memory group.
31 * @present_movable_pages: Present (online) memory in ZONE_MOVABLE of this
32 * memory group.
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | memory.json | 4 …memory accesses issued by the CPU load store unit, where those accesses are issued due to load or …
8 …memory errors (ECC or parity) in protected CPUs RAMs. On the core, this event counts errors in the…
16 …memory accesses issued by the CPU due to load operations. The event counts any memory load access,…
20 …memory accesses issued by the CPU due to store operations. The event counts any memory store acces…
24 …"PublicDescription": "Counts the number of memory read and write accesses in a cycle that incurred…
28 …"PublicDescription": "Counts the number of memory read accesses in a cycle that incurred additiona…
32 …"PublicDescription": "Counts the number of memory write access in a cycle that incurred additional…
36 …cription": "Counts the number of memory read and write accesses counted by MEM_ACCESS that are tag…
40 …"PublicDescription": "Counts the number of memory read accesses in a cycle that are tag checked by…
44 …"PublicDescription": "Counts the number of memory write accesses in a cycle that is tag checked by…
|
| /linux-6.15/tools/perf/pmu-events/arch/arm64/arm/neoverse-n3/ |
| D | memory.json | 4 …memory accesses issued by the CPU load store unit, where those accesses are issued due to load or …
12 …memory accesses issued by the CPU due to load operations. The event counts any memory load access,…
16 …memory accesses issued by the CPU due to store operations. The event counts any memory store acces…
20 …"PublicDescription": "Counts the number of memory read and write accesses in a cycle that incurred…
24 …"PublicDescription": "Counts the number of memory read accesses in a cycle that incurred additiona…
28 …"PublicDescription": "Counts the number of memory write access in a cycle that incurred additional…
32 …cription": "Counts the number of memory read and write accesses counted by MEM_ACCESS that are tag…
36 …"PublicDescription": "Counts the number of memory read accesses in a cycle that are tag checked by…
40 …"PublicDescription": "Counts the number of memory write accesses in a cycle that is tag checked by…
48 … "PublicDescription": "Counts the number of outstanding loads or memory read accesses per cycle."
[all …]
|
| /linux-6.15/tools/testing/selftests/arm64/mte/ |
| D | check_mmap_options.c | 75 /* Only mte enabled memory will allow tag insertion */ in check_anonymous_memory_mapping()
78 ksft_print_msg("FAIL: Insert tags on anonymous mmap memory\n"); in check_anonymous_memory_mapping()
112 /* Only mte enabled memory will allow tag insertion */ in check_file_memory_mapping()
115 ksft_print_msg("FAIL: Insert tags on file based memory\n"); in check_file_memory_mapping()
213 "Check anonymous memory with private mapping, sync error mode, mmap memory and tag check off\n"); in main()
215 …"Check file memory with private mapping, sync error mode, mmap/mprotect memory and tag check off\n… in main()
219 "Check anonymous memory with private mapping, no error mode, mmap memory and tag check off\n"); in main()
221 "Check file memory with private mapping, no error mode, mmap/mprotect memory and tag check off\n"); in main()
224 "Check anonymous memory with private mapping, sync error mode, mmap memory and tag check on\n"); in main()
226 …"Check anonymous memory with private mapping, sync error mode, mmap/mprotect memory and tag check … in main()
[all …]
|
| /linux-6.15/drivers/gpu/drm/nouveau/nvkm/core/ |
| D | memory.c | 24 #include <core/memory.h>
30 nvkm_memory_tags_put(struct nvkm_memory *memory, struct nvkm_device *device, in nvkm_memory_tags_put() argument
39 kfree(memory->tags); in nvkm_memory_tags_put()
40 memory->tags = NULL; in nvkm_memory_tags_put()
48 nvkm_memory_tags_get(struct nvkm_memory *memory, struct nvkm_device *device, in nvkm_memory_tags_get() argument
56 if ((tags = memory->tags)) { in nvkm_memory_tags_get()
57 /* If comptags exist for the memory, but a different amount in nvkm_memory_tags_get()
84 * As memory can be mapped in multiple places, we still in nvkm_memory_tags_get()
94 *ptags = memory->tags = tags; in nvkm_memory_tags_get()
101 struct nvkm_memory *memory) in nvkm_memory_ctor() argument
[all …]
|
| /linux-6.15/Documentation/arch/powerpc/ |
| D | firmware-assisted-dump.rst | 14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
35 - Once the dump is copied out, the memory that held the dump
44 - The first kernel registers the sections of memory with the
46 These registered sections of memory are reserved by the first
50 low memory regions (boot memory) from source to destination area.
54 The term 'boot memory' means size of the low memory chunk
56 booted with restricted memory. By default, the boot memory
58 Alternatively, user can also specify boot memory size
[all …]
|
| /linux-6.15/Documentation/admin-guide/mm/damon/ |
| D | reclaim.rst | 8 be used for proactive and lightweight reclamation under light memory pressure.
10 to be selectively used for different level of memory pressure and requirements.
15 On general memory over-committed systems, proactively reclaiming cold pages
16 helps saving memory and reducing latency spikes that incurred by the direct
20 Free Pages Reporting [3]_ based memory over-commit virtualization systems are
22 memory to host, and the host reallocates the reported memory to other guests.
23 As a result, the memory of the systems are fully utilized. However, the
24 guests could be not so memory-frugal, mainly because some kernel subsystems and
25 user-space applications are designed to use as much memory as available. Then,
26 guests could report only small amount of memory as free to host, results in
[all …]
|
| /linux-6.15/arch/powerpc/kexec/ |
| D | ranges.c | 46 * @mem_rngs: Memory ranges.
61 * Memory is allocated in size multiple of MEM_RANGE_CHUNK_SZ. in get_mem_rngs_size()
68 * __add_mem_range - add a memory range to memory ranges list.
69 * @mem_ranges: Range list to add the memory range to.
71 * @size: Size of the memory range to add.
73 * (Re)allocates memory, if needed.
89 pr_debug("Added memory range [%#016llx - %#016llx] at index %d\n", in __add_mem_range()
96 * __merge_memory_ranges - Merges the given memory ranges list.
140 * sort_memory_ranges - Sorts the given memory ranges list.
161 pr_debug("Memory ranges:\n"); in sort_memory_ranges()
[all …]
|