xe_lrc_get(9)
π xe_lrc_get(9) π
okay bestie, so this one lives in the Kernel API Manual and it's genuinely one of the shortest little icons in the whole drm/xe family β a tiny refcount bump that carries the entire GPU ring context on its shoulders. no cap. let's get into it π«Ά
β¨ NAME β¨
xe_lrc_get β get a reference to the LRC π
like, you're grabbing a ref. that's the whole thing. that's the vibe.
πΈ SYNOPSIS πΈ
struct xe_lrc * xe_lrc_get (struct xe_lrc *lrc );
she takes a pointer and she gives a pointer back. main character behaviour honestly β
π ARGUMENTS π
lrcβ the Logical Ring Context π (yes it's capitalized in the original, yes it's that serious)
that's it. one argument. one queen. one ring context.
π¦ DESCRIPTION π¦
increments the reference count of lrc β¨
that's literally it bestie β it bumps the refcount up by one so the LRC doesn't get yanked out from under you while you're still holding onto it. it's giving protective best friend energy fr fr. no cap. π₯Ί
this is a "get" β the matching "put" is where the refcount comes back down, and it's right there in SEE ALSO if you need it π
π SEE ALSO π
- the kernel file
./drivers/gpu/drm/xe/xe_lrc.hβ go read it, it's giving header-file realness π xe_lrc_put(9)β the other half of the refcount story, the breakup arc πxe_lrc_ring_size(9)β how big the ring is, the measurements are in πxe_lrc_update_timestamp(9)β timestamps, because time is fake but refcounts are real π
and that's the whole page bestie!!! go forth and refcount responsibly β¨ππ
source: ./drivers/gpu/drm/xe β dated October 2026, mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms