Lines Matching refs:mapping

26 #. Support for dynamic mapping and unmapping of regions, even while the MMU is
42 support dynamic mapping. Although potential bug fixes will be applied to both
70 - its mapping granularity (optional).
86 The granularity controls the translation table level to go down to when mapping
93   contains 512 entries, each mapping 4KB).
104 then they might enforce a 4KB mapping granularity for this 2MB region from the
109 library will choose the mapping granularity for this region as it sees fit (more
110 details can be found in `The memory mapping algorithm`_ section below).
178 The library optionally supports dynamic memory mapping. This feature may be
181 When dynamic memory mapping is enabled, the library categorises mmap regions as
190 When the dynamic memory mapping feature is disabled, only static regions exist.
192 The dynamic memory mapping feature may be used to map and unmap transient memory
203 the limits of these allocations ; the library will deny any mapping request that
223 mapping granularity, which leaves the library implementation free to choose
227 As explained earlier in this document, when the dynamic mapping feature is
328 The memory mapping algorithm
331 The mapping function is implemented as a recursive algorithm. It is however
337 favour mapping a region using the biggest possible blocks, only creating a
341 The most common reason for needing a sub-table is when a specific mapping
366 .. [#granularity-ref] That is, when mmap regions do not enforce their mapping
387 dynamic mapping request is deemed legitimate, it automatically concerns memory
392 mapping cannot be cached in the TLBs.