| /linux-3.3/Documentation/ |
| D | memory-hotplug.txt | 2 Memory Hotplug
6 Add description of notifier of memory hotplug Oct 11 2007
8 This document is about memory hotplug including how-to-use and current status.
9 Because Memory Hotplug is still under development, contents of this text will
13 1.1 purpose of memory hotplug
14 1.2. Phases of memory hotplug
15 1.3. Unit of Memory online/offline operation
17 3. sysfs files for memory hotplug
18 4. Physical memory hot-add phase
20 4.2 Notify memory hot-add event by hand
[all …]
|
| D | kmemleak.txt | 1 Kernel Memory Leak Detector
7 Kmemleak provides a way of detecting possible kernel memory leaks in a
12 Valgrind tool (memcheck --leak-check) to detect the memory leaks in
22 thread scans the memory every 10 minutes (by default) and prints the
24 the possible memory leaks:
29 To trigger an intermediate memory scan:
33 To clear the list of all current possible memory leaks:
44 Memory scanning parameters can be modified at run-time by writing to the
50 scan=on - start the automatic memory scanning thread (default)
51 scan=off - stop the automatic memory scanning thread
[all …]
|
| D | bus-virt-phys-mapping.txt | 12 (because all bus master devices see the physical memory mappings directly).
15 at memory addresses, and in this case we actually want the third, the
18 Essentially, the three ways of addressing memory are (this is "real memory",
22 0 is what the CPU sees when it drives zeroes on the memory bus.
28 - bus address. This is the address of memory as seen by OTHER devices,
30 addresses, with each device seeing memory in some device-specific way, but
33 external hardware sees the memory the same way.
37 because the memory and the devices share the same address space, and that is
41 CPU sees a memory map something like this (this is from memory):
43 0-2 GB "real memory"
[all …]
|
| D | DMA-API.txt | 12 memory machines. Unless you know that your driver absolutely has to
29 Consistent memory is memory for which a write by either the device or
33 devices to read that memory.)
35 This routine allocates a region of <size> bytes of consistent memory.
43 Note: consistent memory can be expensive on some platforms, and the
45 consolidate your requests for consistent memory as much as possible.
51 the returned memory, like GFP_DMA).
57 Wraps dma_alloc_coherent() and also zeroes the returned memory if the
64 Free the region of consistent memory you previously allocated. dev,
78 Many drivers need lots of small dma-coherent memory regions for DMA
[all …]
|
| D | atomic_ops.txt | 37 proper implicit or explicit read memory barrier is needed before reading the
55 or explicit memory barrier is needed before the value set with the operation
65 implicit or explicit memory barrier is used after possible runtime
69 interface must take care of that with a proper implicit or explicit memory
79 or processor, and explicitly invoke the appropriate compiler and/or memory
146 and never changed later, so that memory barriers are not needed:
169 Don't even -think- about doing this without proper use of memory barriers,
188 require any explicit memory barriers. They need only perform the
200 Unlike the above routines, it is required that explicit memory
202 done such that all memory operations before and after the atomic
[all …]
|
| /linux-3.3/Documentation/cgroups/ |
| D | memory.txt | 1 Memory Resource Controller
3 NOTE: The Memory Resource Controller has generically been referred to as the
4 memory controller in this document. Do not confuse memory controller
5 used here with the memory controller that is used in hardware.
9 When we mention a cgroup (cgroupfs's directory) with memory controller,
10 we call it "memory cgroup". When you see git-log and source code, you'll
14 Benefits and Purpose of the memory controller
16 The memory controller isolates the memory behaviour of a group of tasks
18 uses of the memory controller. The memory controller can be used to
21 Memory hungry applications can be isolated and limited to a smaller
[all …]
|
| D | cpusets.txt | 22 1.6 What is memory spread ?
40 Cpusets provide a mechanism for assigning a set of CPUs and Memory
41 Nodes to a set of tasks. In this document "Memory Node" refers to
42 an on-line node that contains memory.
44 Cpusets constrain the CPU and Memory placement of tasks to only
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
57 CPUs or Memory Nodes not in that cpuset. The scheduler will not
64 cpusets and which CPUs and Memory Nodes are assigned to each cpuset,
73 complex memory cache hierarchies and multiple Memory Nodes having
75 the efficient scheduling and memory placement of processes.
[all …]
|
| /linux-3.3/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
17 indicates whether this memory block is removable or not.
19 identify removable sections of the memory before attempting
20 potentially expensive hot-remove memory operation
21 Users: hotplug memory remove tools
[all …]
|
| /linux-3.3/Documentation/vm/ |
| D | numa | 10 or more CPUs, local memory, and/or IO buses. For brevity and to
24 Coherent NUMA or ccNUMA systems. With ccNUMA systems, all memory is visible
28 Memory access time and effective memory bandwidth varies depending on how far
29 away the cell containing the CPU or IO bus making the memory access is from the
30 cell containing the target memory. For example, access to memory by CPUs
32 bandwidths than accesses to memory on other, remote cells. NUMA platforms
37 memory bandwidth. However, to achieve scalable memory bandwidth, system and
38 application software must arrange for a large majority of the memory references
39 [cache misses] to be to "local" memory--memory on the same cell, if any--or
40 to the closest cell with memory.
[all …]
|
| D | numa_memory_policy.txt | 2 What is Linux Memory Policy?
4 In the Linux kernel, "memory policy" determines from which node the kernel will
5 allocate memory in a NUMA system or in an emulated NUMA system. Linux has
6 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
7 The current memory policy support was added to Linux 2.6 around May 2004. This
8 document attempts to describe the concepts and APIs of the 2.6 memory policy
11 Memory policies should not be confused with cpusets
14 memory may be allocated by a set of processes. Memory policies are a
17 takes priority. See "MEMORY POLICIES AND CPUSETS" below for more details.
19 MEMORY POLICY CONCEPTS
[all …]
|
| /linux-3.3/mm/ |
| D | Kconfig | 6 prompt "Memory model"
13 bool "Flat Memory"
17 Linux manages its memory internally. Most users will
22 memory hotplug may have different options here.
24 but is incompatible with memory hotplug and may suffer
26 "Sparse Memory" and "Discontiguous Memory", choose
27 "Discontiguous Memory".
29 If unsure, choose this option (Flat Memory) over any other.
32 bool "Discontiguous Memory"
36 memory systems, over FLATMEM. These systems have holes
[all …]
|
| /linux-3.3/include/linux/ |
| D | genalloc.h | 3 * memory, for example, memory that is not managed by the regular
5 * memory, uncached memory etc.
14 * The lockless operation only works if there is enough memory
15 * available. If new memory is added to the pool a lock has to be
17 * that sufficient memory is preallocated.
33 * General purpose special memory pool descriptor.
42 * General purpose special memory pool chunk descriptor.
47 phys_addr_t phys_addr; /* physical starting address of memory chunk */
48 unsigned long start_addr; /* starting address of memory chunk */
49 unsigned long end_addr; /* ending address of memory chunk */
[all …]
|
| D | edac.h | 48 /* memory devices */
69 /* memory types */
175 * Memory devices: The individual chip on a memory stick. These devices
178 * for a memory stick.
180 * Memory Stick: A printed circuit board that aggregates multiple
181 * memory devices in parallel. This is the atomic
182 * memory component that is purchaseable by Joe consumer
183 * and loaded into a memory socket.
186 * a single memory stick.
188 * Channel: Set of memory devices on a memory stick that must be
[all …]
|
| /linux-3.3/arch/blackfin/ |
| D | Kconfig | 365 the memory size and the root device (e.g., mem=8M, root=/dev/nfs).
374 of memory or you wish to reserve some memory at the beginning of
378 memory region is used to capture NULL pointer references as well
511 as the memory device datasheet.
515 menu "Memory Init Control"
690 comment "Memory Optimizations"
693 bool "Locate interrupt entry code in L1 Memory"
698 into L1 instruction memory. (less latency)
701 …ool "Locate entire ASM lowlevel exception / interrupt - Syscall and CPLB handler code in L1 Memory"
706 (STORE/RESTORE CONTEXT) is linked into L1 instruction memory.
[all …]
|
| /linux-3.3/arch/mips/include/asm/octeon/ |
| D | cvmx-bootmem.h | 29 * Simple allocate only memory allocator. Used to allocate memory at
51 /* First bytes of each free physical block of memory contain this structure,
52 * which is used to maintain the free memory list. Since the bootloader is
69 * Structure for named memory blocks. Number of descriptors available
72 * structure must be naturally 64 bit aligned, as a single memory
121 /* address of named memory block descriptors */
127 * Initialize the boot alloc memory structures. This is
130 * @mem_desc_ptr: Address of the free memory list
135 * Allocate a block of memory from the free list that was passed
137 * This is an allocate-only algorithm, so freeing memory is not possible.
[all …]
|
| /linux-3.3/arch/blackfin/kernel/ |
| D | fixed_code.S | 35 * Inputs: P0: memory address to use
37 * Output: R0: old contents of the memory address, zero extended.
48 * Inputs: P0: memory address to use
51 * The new value is stored if the contents of the memory
53 * Output: R0: old contents of the memory address.
67 * Inputs: P0: memory address to use
69 * Outputs: R0: new contents of the memory address.
70 * R1: previous contents of the memory address.
82 * Inputs: P0: memory address to use
84 * Outputs: R0: new contents of the memory address.
[all …]
|
| /linux-3.3/arch/powerpc/mm/ |
| D | numa.c | 184 * Returns the property linux,drconf-usable-memory if
188 static const u32 *of_get_usable_memory(struct device_node *memory) in of_get_usable_memory() argument
192 prop = of_get_property(memory, "linux,drconf-usable-memory", &len); in of_get_usable_memory()
378 struct device_node *memory = NULL; in get_n_mem_cells() local
380 memory = of_find_node_by_type(memory, "memory"); in get_n_mem_cells()
381 if (!memory) in get_n_mem_cells()
382 panic("numa.c: No memory nodes found!"); in get_n_mem_cells()
384 *n_addr_cells = of_n_addr_cells(memory); in get_n_mem_cells()
385 *n_size_cells = of_n_size_cells(memory); in get_n_mem_cells()
386 of_node_put(memory); in get_n_mem_cells()
[all …]
|
| /linux-3.3/arch/ia64/include/asm/ |
| D | gcc_intrin.h | 17 #define ia64_barrier() asm volatile ("":::"memory")
25 #define ia64_flushrs() asm volatile ("flushrs;;":::"memory")
27 #define ia64_loadrs() asm volatile ("loadrs;;":::"memory")
40 asm volatile ("mov psr.l=%0" :: "r"(val) : "memory"); \
45 "r"(val): "memory"); \
50 "r"(val): "memory" ); \
54 "r"(val): "memory"); \
57 asm volatile ("mov gp=%0" :: "r"(val) : "memory"); \
106 asm volatile ("hint @pause" ::: "memory"); \
209 asm volatile ("stfs [%0]=%1" :: "r"(x), "f"(__f__) : "memory"); \
[all …]
|
| /linux-3.3/drivers/xen/ |
| D | Kconfig | 5 bool "Xen memory balloon driver"
8 The balloon driver allows the Xen domain to request more memory from
9 the system to expand the domain's memory allocation, or alternatively
10 return unneeded memory to the system.
13 bool "Dynamically self-balloon kernel memory to target"
17 Self-ballooning dynamically balloons available kernel memory driven
18 by the current usage of anonymous memory ("committed AS") and
30 bool "Memory hotplug support for Xen balloon driver"
34 Memory hotplug support for Xen balloon driver allows expanding memory
39 Memory could be hotplugged in following steps:
[all …]
|
| /linux-3.3/drivers/staging/tidspbridge/include/dspbridge/ |
| D | rmm.h | 6 * This memory manager provides general heap management and arbitrary
7 * alignment for any number of memory segments, and management of overlay
8 * memory.
35 * Memory segment on the DSP available for remote allocations.
52 * rmm_alloc is used to remotely allocate or reserve memory on the DSP.
56 * segid - Memory segment to allocate from.
62 * reserve - If TRUE, reserve the memory specified by dsp_address.
65 * -ENOMEM: Memory allocation on GPP failed.
66 * -ENXIO: Cannot "allocate" overlay memory because it's
81 * Create a target object with memory segments for remote allocation. If
[all …]
|
| /linux-3.3/tools/perf/ |
| D | perf.h | 10 #define rmb() asm volatile("lock; addl $0,0(%%esp)" ::: "memory")
11 #define cpu_relax() asm volatile("rep; nop" ::: "memory");
20 #define rmb() asm volatile("lfence" ::: "memory")
21 #define cpu_relax() asm volatile("rep; nop" ::: "memory");
30 #define rmb() asm volatile ("sync" ::: "memory")
31 #define cpu_relax() asm volatile ("" ::: "memory");
37 #define rmb() asm volatile("bcr 15,0" ::: "memory")
38 #define cpu_relax() asm volatile("" ::: "memory");
44 # define rmb() asm volatile("synco" ::: "memory")
46 # define rmb() asm volatile("" ::: "memory")
[all …]
|
| /linux-3.3/Documentation/ia64/ |
| D | aliasing.txt | 1 MEMORY ATTRIBUTE ALIASING ON IA-64
8 MEMORY ATTRIBUTES
10 Itanium supports several attributes for virtual memory references.
19 System memory typically uses the WB attribute. The UC attribute is
20 used for memory-mapped I/O devices. The WC attribute is uncacheable
29 support either WB or UC access to main memory, while others support
32 MEMORY MAP
34 Platform firmware describes the physical memory map and the
36 the EFI GetMemoryMap() interface. ACPI can also describe memory
47 memory Linux is actually using and the attribute for each region.
[all …]
|
| /linux-3.3/lib/ |
| D | genalloc.c | 3 * memory, for example, memory that is not managed by the regular
5 * memory, uncached memory etc.
14 * The lockless operation only works if there is enough memory
15 * available. If new memory is added to the pool a lock has to be
17 * that sufficient memory is preallocated.
139 * gen_pool_create - create a new special memory pool
143 * Create a new special memory pool that can be used to manage special purpose
144 * memory not managed by the regular kmalloc/kfree interface.
161 * gen_pool_add_virt - add a new chunk of special memory to the pool
162 * @pool: pool to add new memory chunk to
[all …]
|
| /linux-3.3/arch/microblaze/ |
| D | Kconfig | 139 aspects of kernel memory management.
151 This is needed to be able to allocate uncachable memory regions.
152 The feature requires the design to define the RAM memory controller
153 window to be twice as large as the actual physical memory.
156 bool "Set high memory pool address"
160 area used to map high memory pages. This can be useful in
161 optimizing the layout of kernel virtual memory.
166 hex "Virtual start address of high memory pool" if HIGHMEM_START_BOOL
171 bool "Set maximum low memory"
174 This option allows you to set the maximum amount of memory which
[all …]
|
| /linux-3.3/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 1 This document describes the cx2341x memory map and documents some of the register
4 Note: the memory long words are little-endian ('intel format').
6 Warning! This information was figured out from searching through the memory and
8 was not derived from anything more than searching through the memory space with
16 Memory Map
19 The cx2341x exposes its entire 64M memory space to the PCI host via the PCI BAR0
23 0x00000000-0x00ffffff Encoder memory space
30 0x01000000-0x01ffffff Decoder memory space
68 0x80 - first write linked list reg, for Encoder Memory addr
69 0x84 - first write linked list reg, for pci memory addr
[all …]
|