drm_gem_lru_move_tail(9)

💖 drm_gem_lru_move_tail(9) — Kernel API Manual 💖

Okay bestie, this is the drm_gem_lru_move_tail(9) page from the Kernel API Manual, and it's lowkey just one tiny LRU shuffle. Let's get into it ✨

🎀 NAME 🎀

drm_gem_lru_move_tail — move the object to the tail of the LRU

✨ SYNOPSIS ✨

void drm_gem_lru_move_tail (struct drm_gem_lru *lru , struct
       drm_gem_object *obj );

🫶 ARGUMENTS 🫶

• lru — the LRU you're moving the object into. That's the destination, bestie 💅
• obj — the GEM object that's getting moved into this LRU.

🌸 DESCRIPTION 🌸

So here's the tea: if the object is already in this LRU, it gets moved to the tail. Periodt. 🎀

Otherwise, it gets removed from whichever other LRU it's in (if any), and then moved into this LRU. That's the whole move, no cap. 🦋

🌈 SEE ALSO 🌈

The kernel file is ./drivers/gpu/drm/drm_gem.c, and the related-functions group chat is:

• drm_gem_huge_mnt_create(9)
• drm_gem_init(9)
• drm_gem_object_init(9)
• drm_gem_private_object_init(9)
• drm_gem_private_object_fini(9)
• drm_gem_object_handle_get_if_exists_unlocked(9)
• drm_gem_object_handle_free(9)
• drm_gem_object_handle_put_unlocked(9)
• drm_gem_handle_delete(9)
• drm_gem_dumb_map_offset(9)
• drm_gem_handle_create_tail(9)
• drm_gem_handle_create(9)
• drm_gem_free_mmap_offset(9)
• drm_gem_create_mmap_offset_size(9)
• drm_gem_create_mmap_offset(9)
• drm_gem_get_pages(9)
• drm_gem_put_pages(9)
• drm_gem_objects_lookup(9)
• drm_gem_object_lookup(9)
• drm_gem_dma_resv_wait(9)
• drm_gem_open(9)
• drm_gem_release(9)
• drm_gem_object_release(9)
• drm_gem_object_free(9)
• drm_gem_vm_open(9)
• drm_gem_vm_close(9)
• drm_gem_mmap_obj(9)
• drm_gem_get_unmapped_area(9)
• drm_gem_mmap(9)
• drm_gem_lock_reservations(9)
• drm_gem_lru_init(9)
• drm_gem_lru_remove(9)
• drm_gem_lru_move_tail_locked(9)
• drm_gem_lru_scan(9)
• drm_gem_evict_locked(9)

That's the vibe check, bestie 🫶 Source/version: ./drivers/gpu/drm; date: October 2026; manual: drm_gem_lru_move_tail(9). Mwah 💋