| /freebsd/share/doc/papers/kernmalloc/ |
| H A D | kernmalloc.t | 74 Design of a General Purpose Memory Allocator for the 4.3BSD UNIX\(dg Kernel
78 .EH 'Design of a General Purpose Memory ...''McKusick, Karels'
79 .OH 'McKusick, Karels''Design of a General Purpose Memory ...'
94 The 4.3BSD UNIX kernel uses many memory allocation mechanisms,
96 This paper describes a general purpose dynamic memory allocator
98 The design of this allocator takes advantage of known memory usage
101 This allocator replaces the multiple memory allocation interfaces
103 results in more efficient use of global memory by eliminating
104 partitioned and specialized memory pools,
108 the new memory allocator,
[all …]
|
| /freebsd/lib/libmemstat/ |
| H A D | libmemstat.3 | 30 .Nd "library interface to retrieve kernel memory allocator statistics"
39 .Ss Memory Type List Management Functions
67 .Ss Memory Type Accessor Methods
144 provides an interface to retrieve kernel memory allocator statistics, for
153 describes each memory type using a
155 an opaque memory type accessed by the application using accessor functions
166 Lists of memory types are populated via calls that query the kernel for
175 Repeated calls will incrementally update the list of memory types, permitting
183 Freeing the list will free all memory type data in the list, and so
203 holds a description of the memory type, including its name and the allocator
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/memory-controllers/fsl/ |
| H A 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 …]
|
| /freebsd/contrib/ofed/include/ |
| H A D | udma_barrier.h | 47 - CPU attached address space (the CPU memory could be a range of things:
58 same memory location.
65 /* Ensure that the device's view of memory matches the CPU's view of memory.
76 writes could be to any CPU mapped memory object with any cachability mode.
79 only fenced normal stores to normal memory. libibverbs users using other
80 memory types or non-temporal stores are required to use SFENCE in their own
84 #define udma_to_device_barrier() asm volatile("" ::: "memory")
86 #define udma_to_device_barrier() asm volatile("" ::: "memory")
88 #define udma_to_device_barrier() asm volatile("sync" ::: "memory")
90 #define udma_to_device_barrier() asm volatile("sync" ::: "memory")
[all …]
|
| /freebsd/contrib/opencsd/decoder/include/common/ |
| H A D | ocsd_dcd_tree.h | 226 * Set a target memory access interface - used to access program image memory for instruction
236 /** @name Memory Access Mapper
238 A memory mapper is used to organise a collection of memory accessor objects that contain the
239 … memory images for different areas of traced instruction memory. These areas could be the executed
241 different memory locations.
243 … A memory accessor represents a snapshot of an area of memory as it appeared during trace capture,
244 for a given memory space. Memory spaces are described by the ocsd_mem_space_acc_t enum. The most
245 …general memory space is OCSD_MEM_SPACE_ANY. This represents memory that can be secure or none-secu…
248 The memory mapper will not allow two accessors to overlap in the same memory space.
250 …The trace decdoer will access memory with a memory space parameter that represents the current core
[all …]
|
| /freebsd/share/doc/papers/newvm/ |
| H A D | 1.t | 29 Motivations for a New Virtual Memory System
31 The virtual memory system distributed with Berkeley UNIX has served
38 be taken into account in a new virtual memory design.
40 Implementation of 4.3BSD virtual memory
43 have used the same virtual memory design.
53 Thus, the limit to available virtual memory is established by the
56 Memory pages are used in a sort of shell game to contain the
68 Design assumptions for 4.3BSD virtual memory
70 The design criteria for the current virtual memory implementation
72 At that time the cost of memory was about a thousand times greater per
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | shm_open.2 | 34 .Nd "shared memory object operations"
62 shared memory object named
84 then a new shared memory object named
88 the shared memory object is created with mode
95 flags are specified and a shared memory object named
104 If an existing shared memory object is opened with
109 then the shared memory object will be truncated to a size of zero.
129 In this case, an anonymous, unnamed shared memory object is created.
136 the shared memory object will be garbage collected when the last reference to
137 the shared memory object is removed.
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Support/ |
| H A D | Memory.h | 1 //===- llvm/Support/Memory.h - Memory Support -------------------*- C++ -*-===//
9 // This file declares the llvm::sys::Memory class.
26 /// This class encapsulates the notion of a memory block which has an address
27 /// and a size. It is used by the Memory class (a friend) as the result of
28 /// various memory allocation operations.
29 /// @see Memory
30 /// Memory block abstraction.
42 void *Address; ///< Address of first byte of memory area
43 size_t AllocatedSize; ///< Size, in bytes of the memory area
45 friend class Memory; variable
[all …]
|
| H A D | ModRef.h | 1 //===--- ModRef.h - Memory effect modelling ---------------------*- C++ -*-===//
10 // describe the memory effects of instructions.
23 /// Flags indicating whether a memory access modifies or references memory.
28 /// The access neither references nor modifies the value stored in memory.
30 /// The access may reference the value stored in memory.
32 /// The access may modify the value stored in memory.
34 /// The access may reference and may modify the value stored in memory.
58 /// The locations at which a function might access memory.
60 /// Access to memory via argument pointers.
62 /// Memory that is inaccessible via LLVM IR.
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | proto.4 | 117 .Ss Memory mapped I/O resources
118 The device special files created for memory mapped I/O resources behave
120 Additionally, device special files for memory mapped I/O resources allow
121 the memory to be mapped into the process' address space using
123 Reads and writes to the memory address returned by
133 Also, make sure the compiler does not optimize memory accesses away or has
192 An object is either a tag or a memory descriptor (md).
227 This means that derived tags that have this tag as a parent and memory
230 Allocate memory that satisfies the constraints put forth by the tag
236 The key of the memory descriptor for this memory is returned in the
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | BIO_s_mem.pod | 7 BIO_get_mem_ptr, BIO_new_mem_buf - memory BIO
25 BIO_s_mem() returns the memory BIO method function.
27 A memory BIO is a source/sink BIO which uses memory for its I/O. Data
28 written to a memory BIO is stored in a BUF_MEM structure which is extended
34 Any data written to a memory BIO can be recalled by reading from it.
35 Unless the memory BIO is read only any data read from it is deleted from
38 Memory BIOs support BIO_gets() and BIO_puts().
40 If the BIO_CLOSE flag is set when a memory BIO is freed then the underlying
43 Calling BIO_reset() on a read write memory BIO clears any data in it if the
53 BIO_set_mem_eof_return() sets the behaviour of memory BIO B<b> when it is
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/reserved-memory/ |
| H A D | reserved-memory.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/reserved-memory.yaml#
7 title: /reserved-memory Child Node Common
13 Reserved memory is specified as a node under the /reserved-memory node. The
14 operating system shall exclude reserved memory from normal usage one can
16 memory regions. Such memory regions are usually designed for the special
19 Each child of the reserved-memory node specifies one or more regions
20 of reserved memory. Each child node may either use a 'reg' property to
21 specify a specific range of reserved memory, or a 'size' property with
23 memory.
38 Length based on parent's \#size-cells. Size in bytes of memory to
[all …]
|
| /freebsd/contrib/llvm-project/lldb/include/lldb/API/ |
| H A D | SBMemoryRegionInfo.h | 34 /// Get the base address of this memory range.
37 /// The base address of this memory range.
40 /// Get the end address of this memory range.
43 /// The base address of this memory range.
46 /// Check if this memory address is marked readable to the process.
49 /// true if this memory address is marked readable
52 /// Check if this memory address is marked writable to the process.
55 /// true if this memory address is marked writable
58 /// Check if this memory address is marked executable to the process.
61 /// true if this memory address is marked executable
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | OF_getprop.9 | 124 into the memory specified by
132 bytes into memory specified by
156 into the memory specified by
170 into the memory specified by
177 allocates memory large enough to hold the
182 and copies the value into the newly allocated memory region.
184 the address of the allocated memory in
190 memory allocation failed.
191 Allocated memory should be released when no longer required
194 The function might sleep when allocating memory.
[all …]
|
| H A D | kmsan.9 | 33 .Nd Kernel Memory SANitizer
64 uninitialized memory in the kernel.
70 calls preceding memory accesses.
75 When uninitialized memory is used as a source operand in certain operations,
76 such as control flow expressions or memory accesses, the runtime reports
82 call which copies uninitialized memory will cause the destination buffer or
92 uninitialized memory is included.
94 In addition to compiler-detected uses of uninitialized memory,
134 For example, when a piece of memory is freed to a kernel allocator, it will
135 typically have been marked initialized; before the memory is reused for a new
[all …]
|
| H A D | malloc.9 | 50 .Nd kernel memory management routines
102 function allocates uninitialized memory in kernel address space for an
108 variant allocates memory from a specific
127 can be used to return executable memory.
129 memory.
133 function allocates uninitialized memory in kernel address space for an
141 variant allocates memory from a specific
150 function releases memory at address
155 The memory is not zeroed.
168 function releases memory at address
[all …]
|
| H A D | bus_dma.9 | 163 Direct Memory Access (DMA) is a method of transferring data
165 A DMA transaction can be achieved between device to memory,
166 device to device, or memory to memory.
207 represents a mapping of a memory region for DMA.
214 a mapping must be bound to a memory region by calling one of the
222 engine to access the memory region.
232 the sync operations copy data between the bounce pages and the memory region
235 flushing and CPU memory operation ordering.
239 Static transactions are used with a long-lived memory region that is reused
247 Static transactions use memory regions allocated by
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/cascadelakex/ |
| H A D | uncore-memory.json | 3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
13 "BriefDescription": "read requests to memory controller",
23 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
33 "BriefDescription": "write requests to memory controller",
43 "BriefDescription": "Memory controller clock ticks",
60 "BriefDescription": "Cycles Memory is in self refresh power mode",
88 …": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
96 …": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC persistent memory",
104 …"BriefDescription": "Intel Optane DC persistent memory bandwidth read (MB/sec). Derived from unc_m…
113 "BriefDescription": "Intel Optane DC persistent memory bandwidth read (MB/sec)",
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/fsl/ |
| H A D | fsl,qman-fqd.yaml | 7 title: QMan Private Memory Nodes
13 QMan requires two contiguous range of physical memory used for the backing store
15 This memory is reserved/allocated as a node under the /reserved-memory node.
17 BMan requires a contiguous range of physical memory used for the backing store
18 for BMan Free Buffer Proxy Records (FBPR). This memory is reserved/allocated as
19 a node under the /reserved-memory node.
21 The QMan FQD memory node must be named "qman-fqd"
22 The QMan PFDR memory node must be named "qman-pfdr"
23 The BMan FBPR memory node must be named "bman-fbpr"
25 The following constraints are relevant to the FQD and PFDR private memory:
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/ExecutionEngine/ |
| H A D | SectionMemoryManager.h | 1 //===- SectionMemoryManager.h - Memory manager for MCJIT/RtDyld -*- C++ -*-===//
9 // This file contains the declaration of a section-based memory manager used by
19 #include "llvm/Support/Memory.h"
26 /// This is a simple memory manager which implements the methods called by
27 /// the RuntimeDyld class to allocate memory for section-based loading of
30 /// This memory manager allocates all section memory as read-write. The
31 /// RuntimeDyld will copy JITed section memory into these allocated blocks
34 /// Any client using this memory manager MUST ensure that section-specific
53 /// This method attempts to allocate \p NumBytes bytes of virtual memory for
55 /// case an attempt is made to allocate more memory near the existing block.
[all …]
|
| /freebsd/contrib/opencsd/decoder/include/interfaces/ |
| H A D | trc_tgt_mem_access_i.h | 3 * \brief OpenCSD : Target memory read interface.
41 * @brief Interface to target memory access.
45 * Read Target memory call is used by the decoder to access the memory location in the
46 * target memory space for the next instruction(s) to be traced.
48 * Memory data returned is to be little-endian.
50 * The implementator of this interface could either use file(s) containing dumps of memory
63 * Read a block of target memory into supplied buffer.
65 … * Bytes read set less than bytes required, along with a success return code indicates full memory
69 …* The cs_trace_id associates a memory read with a core. Different cores may have different memory …
70 …* the memory access may take this into account. Access will first look in the registered memory ar…
[all …]
|
| /freebsd/stand/efi/include/ |
| H A D | efipciio.h | 2 EFI PCI I/O Protocol provides the basic Memory, I/O, PCI configuration,
54 #define EFI_PCI_IO_PASS_THROUGH_BAR 0xff ///< Special BAR that passes a memory or …
55 #define EFI_PCI_IO_ATTRIBUTE_MASK 0x077f ///< All the following I/O and Memory cyc…
63 #define EFI_PCI_IO_ATTRIBUTE_MEMORY_WRITE_COMBINE 0x0080 ///< Map a memory range so writes are com…
65 #define EFI_PCI_IO_ATTRIBUTE_MEMORY 0x0200 ///< Enable the Memory decode bit in the …
67 #define EFI_PCI_IO_ATTRIBUTE_MEMORY_CACHED 0x0800 ///< Map a memory range so all r/w access…
68 #define EFI_PCI_IO_ATTRIBUTE_MEMORY_DISABLE 0x1000 ///< Disable a memory range
86 /// A read operation from system memory by a bus master.
90 /// A write operation from system memory by a bus master.
94 /// Provides both read and write access to system memory by both the processor and a
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/ExecutionEngine/Orc/ |
| H A D | OrcABISupport.h | 97 /// Write the resolver code into the given memory. The user is
98 /// responsible for allocating the memory and setting permissions.
109 /// Write the requested number of trampolines into the given memory,
117 /// Write NumStubs indirect stubs to working memory at StubsBlockWorkingMem.
119 /// Nth stub using the Nth pointer in memory starting at
137 /// Write the requested number of trampolines into the given memory,
145 /// Write NumStubs indirect stubs to working memory at StubsBlockWorkingMem.
147 /// Nth stub using the Nth pointer in memory starting at
162 /// Write the resolver code into the given memory. The user is
163 /// responsible for allocating the memory and setting permissions.
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/Support/Windows/ |
| H A D | Memory.inc | 1 //===- Win32/Memory.cpp - Win32 Memory Implementation -----------*- C++ -*-===//
9 // This file provides the Win32 specific implementation of various Memory
23 switch (Flags & llvm::sys::Memory::MF_RWE_MASK) {
26 case llvm::sys::Memory::MF_READ:
28 case llvm::sys::Memory::MF_WRITE:
31 case llvm::sys::Memory::MF_READ | llvm::sys::Memory::MF_WRITE:
33 case llvm::sys::Memory::MF_READ | llvm::sys::Memory::MF_EXEC:
35 case llvm::sys::Memory::MF_READ | llvm::sys::Memory::MF_WRITE |
36 llvm::sys::Memory::MF_EXEC:
38 case llvm::sys::Memory::MF_EXEC:
[all …]
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | c.t | 38 information to be emitted by protocols, fragment host memory,
40 such as these, most systems allocate a fixed pool of memory
45 respect. At boot time a fixed amount of memory is allocated by
46 the networking system. At later times more system memory
48 memory ever returned to the system. It is possible to
49 garbage collect memory from the network, but difficult. In
65 Memory management
67 The basic memory allocation routines manage a private page map,
68 the size of which determines the maximum amount of memory
70 A small amount of memory is allocated at boot time
[all …]
|