Expand description
persist — one resident worker per site loops over ITS work items (the “persistent kernel”).
Where a site owns more than one work item, every engine program of the site is wrapped in an outer
item loop; the tile addresses are already affine in the item coordinates (LV_ITEM_Y / LV_ITEM_X),
which the choreography derives from the item index. Multicast groups whose members own different item
counts would pair blocks with nothing on the far side — refused typed.