A warp scheduler keeps an SM busy by issuing work from a ready warp when another warp is waiting for memory. Think of a barista taking another order while milk steams: the waiting warp’s registers are already resident, so switching requires no save-and-restore step. This helps hide memory latency. section 14.1
Taking turns during a memory wait
If a warp computes for 25 cycles and then waits 400 cycles for memory, roughly 16 warps can take turns computing during that wait. With too few warps, the SM may sit idle; with more, a warp is more likely to be ready. This is a simplified single-pipe picture; real SMs have several warp schedulers. section 14.1
