drm_gem_lru_..._tail_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_gem_lru_move_tail_locked β€” Kernel API Manual ✨

okay bestie, gather round, because today we're talking about drm_gem_lru_move_tail_locked(9) from the Kernel API Manual, and honestly? she's short, she's sweet, she's locked. let's get into it 🫢


🌸 NAME 🌸

drm_gem_lru_move_tail_locked β€” move the object to the tail of the LRU πŸŽ€

like, literally that's her whole job. no cap.


✨ SYNOPSIS ✨

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

she's a void function, so don't go looking for a return value, bestie β€” there isn't one πŸ’€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lru β€” The LRU to move the object into. this is the queue she's sliding into, periodt πŸ’…
  • obj β€” The GEM object to move into this LRU. the actual star of the show, the main character πŸ‘‘

🌈 DESCRIPTION 🌈

okay so here's the vibe: this is like drm_gem_lru_move_tail β€” same energy, same tail-moving situation β€” but the lru lock must be held πŸ”’

that's it. that's the whole twist. the _locked in the name is not decorative, bestie, it's a whole warning label. hold the lock, or it's giving undefined behaviour 😭


πŸ’– SEE ALSO πŸ’–

the whole friend group, no gatekeeping:

Kernel file ./drivers/gpu/drm/drm_gem.c


🧚 quick reminder before you go: _locked means the lru lock is already held. do not come for me if you skip that part, i warned you πŸ’€

and that's the whole page, bestie 🌸 this cutie lives at ./drivers/gpu/drm, dated October 2026, and she's filed under drm_gem_lru_..._tail_locked(9) β€” mwah, slay, periodt πŸ’…πŸ’–

πŸ“¦ where this page comes from