xe_drm_client_add_bo(9)
β¨ NAME β¨
okay bestie, this is xe_drm_client_add_bo(9) from the Kernel API Manual, and the name is literally xe_drm_client_add_bo - Add BO for tracking client mem usage. π
that's the whole vibe.
π¦ SYNOPSIS π¦
here's the exact signature, no cap:
void xe_drm_client_add_bo (struct xe_drm_client *client , struct xe_bo
*bo );
πΈ ARGUMENTS πΈ
clientβ the drm client ptr β the main character pointer. πboβ the xe BO ptr β the BO in question. π
π DESCRIPTION π
so here's the tea: you add all BO created by individual drm client by calling this function. this helps in tracking client memory usage. it's giving memory-usage accounting, and honestly? iconic. π₯
π«Ά RETURN π«Ά
void β literally nothing comes back. the function is voiding, and that's the whole return situation. π
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/xe/xe_drm_client.c DRM Client usage stats(9)xe_drm_client_alloc(9)__xe_drm_client_free(9)xe_drm_client_remove_bo(9)xe_drm_client_fdinfo(9)
go read these if you want the full lore. π
mwah π this page came from ./drivers/gpu/drm/xe, dated October 2026, and it's literally xe_drm_client_add_bo(9). bye bestie, slay your BO tracking. π«Άβ¨
π¦ 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