DRM_SCHED_F...DEADLINE_BIT(9)
π DRM_SCHED_F...DEADLINE_BIT(9) π
okay so bestie, this page is from the Kernel API Manual and it's lowkey short but it's important, so pay attention π«Ά
β¨ NAME β¨
DRM_SCHED_FENCE_FLAG_HAS_DEADLINE_BIT β a fence deadline hint has been set π
β¨ SYNOPSIS β¨
DRM_SCHED_FENCE_FLAG_HAS_DEADLINE_BIT
that's it. that's the whole synopsis. she's literally just a flag, no cap π
β¨ DESCRIPTION β¨
okay so here's the tea β β the reason this flag exists at all is that a deadline hint can get set before the backing hw fence is even created. like, the hint shows up early, before the fence has made its grand entrance π
so because of that, we need to keep track of whether a deadline has already been set. that's it. that's the whole job. she's a "yes, we already did that" receipt and she takes it very seriously π β¨
β¨ SEE ALSO β¨
- Kernel file
./include/drm/gpu_scheduler.hβ go read it, iykyk π DRM_SCHED_FENCE_DONT_PIPELINE(9)struct drm_sched_entity(9)struct drm_sched_rq(9)struct drm_sched_fence(9)struct drm_sched_job(9)enum drm_gpu_sched_stat(9)struct drm_sched_backend_ops(9)struct drm_gpu_scheduler(9)struct drm_sched_init_args(9)struct drm_sched_pending_job_iter(9)drm_sched_for_each_pending_job(9)
like a whole little friend group of scheduler structs πΈ go say hi to all of them fr fr
π and that's the page!! brought to you from ./include/drm, dated October 2026 β mwah, love that for us. slay, bye besties ππ¦
π¦ 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