drm_sched_get_finished_job(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_sched_get_finished_job(9) β€” from the Kernel API Manual, bestie

okay so picture this: we're deep in the kernel API manual, section drm_sched_get_finished_job(9), and this little function is literally the cleanup crew of the GPU scheduler. main character energy, fr fr.


✨ NAME ✨

drm_sched_get_finished_job β€” grab the next finished job so it can get destroyed πŸ‘‘πŸ’€


🌸 SYNOPSIS 🌸

struct drm_sched_job * drm_sched_get_finished_job (struct
       drm_gpu_scheduler *sched );

like… it hands you back a struct drm_sched_job *, no cap 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • sched β€” the scheduler instance. that's it, that's the whole vibe ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: this function lets the caller know, through have_more, whether there are more finished jobs hanging around besides the one it just returned. iykyk πŸ’…

it returns the next finished job from the pending list (if there even is one) all ready for its little glow-up into being destroyed. iconic behavior honestly 🌈⭐

lowkey important: the returned job is ready to be destroyed β€” that's literally its whole purpose, don't skip that part πŸ™ˆ

πŸ’œ SEE ALSO πŸ’œ

bestie there is SO much more lore, go read these too:


okay that's the whole page, bestie, you ate that πŸ“

and for the receipts: this one lives over in ./drivers/gpu/drm/scheduler, dated October 2026, and it's still filed under drm_sched_get_finished_job(9) β€” periodt πŸ’–πŸ§š

πŸ“¦ where this page comes from