Lines Matching defs:memory
2 drm-memory
21 Many modern high-end GPUs come with their own memory managers. They even
23 Textures, framebuffers, command buffers and more need to be stored in memory
24 that can be accessed quickly by the GPU. Therefore, memory management on GPUs
37 scanout. These buffers can be memory mapped via **mmap**\ (2) so you can render
47 requests the DRM subsystem to prepare the buffer for memory-mapping and returns
74 is used by several other calls that take a gem-handle or memory-buffer as
116 *TTM* stands for *Translation Table Manager* and is a generic memory-manager
119 radeon man pages for more information on memory-management with radeon and TTM.
125 memory-management framework in the kernel, that is used by many different
126 drivers. GEM is designed to manage graphics memory, control access to the
131 ensuring that the correct memory synchronization occurs.
137 memory-management with driver-dependent ioctls. This manpage tries to describe
147 Gem provides explicit memory management primitives. System pages are allocated
149 where system memory is used by the graphics processor directly, or as backing
150 store for graphics-processor resident memory.
241 This section includes examples for basic memory-management tasks.
248 and provides memory-mapped buffers that can be used for scanout. This
283 /* prepare buffer for memory mapping */
293 /* perform actual memory mapping */
296 /* memory-mapping failed; see "errno" */