Skip to main content

Module launched

Module launched 

Source
Expand description

The kernels a workload launches, collected while it replays: what an environment shipped for that workload has to keep, and all it has to.

A build compiles far more than it ships — every candidate an autotune race measured, of which only the winner is ever launched again. Replaying the workload the environment is shipped for, under a LaunchedKernels, names exactly the kernels it runs; everything else in the compilation store can go. The replay may be a dry run: a dropped launch is still issued, and so still collected.

Collected on the issuing thread, where every backend’s launch passes, by the stable hash that also names a kernel’s artifact in the compilation store. Outside a collection a launch pays one relaxed atomic load.

Structs§

LaunchedKernels
Collects every kernel launched, on every thread and device, from new to finish. Collections may overlap: each sees what was launched while it was open, and nothing before.