ttm_bo_evict_first(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ttm_bo_evict_first(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel API manual, section 9, and you've stumbled onto ttm_bo_evict_first. Welcome, bestie, you're gonna slay this one. ✨

🌸 NAME 🌸

ttm_bo_evict_first — evict the first bo on the manager's LRU list. that's it, that's the whole vibe. one (1) bo, first in line, getting evicted. it's giving "line leader gets told to leave" energy 💀

✨ SYNOPSIS ✨

int ttm_bo_evict_first (struct ttm_device *bdev , struct
       ttm_resource_manager *man , struct ttm_operation_ctx *ctx );

yes she takes three (3) args and returns an int. no cap. 🫶

🎀 ARGUMENTS 🎀

  • bdev — the ttm device. this is the whole device we're working with, the main character of the hardware situation 👑
  • man — the manager whose bo to evict. literally the manager. and whose bo we're kicking out. respect the possessiveness, it's important 💅
  • ctx — the TTM operation ctx governing the eviction. the rules of engagement, the vibe check for the whole eviction, yk? 🦋

⭐ RETURN ⭐

returns 0 if it worked OR if the resource just... disappeared (gone, vanished, no notes 😭), and a negative error code on error. so like, zero is the good outcome, negative means something went sideways. periodt. 🔥

ngl, the "or the resource disappeared" clause is doing a lot of heavy lifting here — zero covers success and the resource peacing out, so don't go assuming a 0 means the resource is still around. it's giving "ambiguous but fine" energy 🙈

🌈 SEE ALSO 🌈

the whole friend group, fr fr — all of these live right here in the kernel file ./drivers/gpu/drm/ttm/ttm_bo.c:

like, go read them, iykyk 💖

and that's the page !! sourced from ./drivers/gpu/drm/ttm, dated October 2026, and it's ttm_bo_evict_first(9) and she ate, no crumbs 🍓🧚💜

📦 where this page comes from