Warp execution state
A resident warp holds execution state on an SM. An eligible warp has an instruction ready to issue. An issued warp is one selected by the scheduler at that issue opportunity.
How it works
Resident warps can wait for dependencies, barriers or an unavailable pipeline. Eligible but unselected warps supply alternative ready work. These categories must be read at the same scheduler, cycle and measurement scope.
Four resident warps. Two ready. One selected.
Work through an example
Imagine four resident warps: A waits for a load, B waits at a barrier, and C and D are ready. Selecting C leaves D eligible but not selected. Residency is four; readiness is two; one warp issues.
Where the term can mislead
“Active” in an occupancy metric usually means resident. It does not mean the warp issued an instruction in that cycle.
Connect the idea
Take it into practice
Continue with the existing concept, apply it to an interview problem, or follow a course lesson. Access requirements are shown before you open a page.
New to GPUs? Start with the free execution-model concept.
Sources and scope
Examples here are teaching calculations, not measured GPU performance. Consult the linked documentation for the exact device, instruction and tool version. Source review: 25 October 2026.
