Lines Matching full:allocator
56 * drm_mm provides a simple range allocator. The drivers are free to use the
57 * resource allocator from the linux core if it suits them, the upside of drm_mm
67 * The range allocator also supports reservation of preallocated blocks. This is
71 * after the allocator is initialized, which helps with avoiding looped
93 * some basic allocator dumpers for debugging.
95 * Note that this range allocator is not thread-safe, drivers need to protect
438 * @mm: drm_mm allocator to insert @node into
441 * This functions inserts an already set-up &drm_mm_node into the allocator,
443 * fields must be cleared to 0. This is useful to initialize the allocator with
444 * preallocated objects which must be set-up before the range allocator can be
620 * drm_mm_remove_node - Remove a memory node from the allocator.
623 * This just removes a node from its drm_mm allocator. The node does not need to
625 * allocator. It is a bug to call this function on a unallocated node.
653 * @old: drm_mm_node to remove from the allocator
696 * The DRM range allocator supports this use-case through the scanning
706 * order to restore the allocator state. Note that while the allocator is used
956 * drm_mm_init - initialize a drm-mm allocator
991 * drm_mm_takedown - clean up a drm_mm allocator
992 * @mm: drm_mm allocator to clean up
994 * Note that it is a bug to call this function on an allocator which is not
1019 * drm_mm_print - print allocator state
1020 * @mm: drm_mm allocator to print