parsec icon indicating copy to clipboard operation
parsec copied to clipboard

Provide API to map real device ID to parsec ID and back

Open devreal opened this issue 9 months ago • 5 comments

Description

PaRSEC numbers its devices differently from the rest of world (starting with 0 for host, possibly 1 for recursive, 2... for devices). CUDA and HIP start numbering devices from 0.

Describe the solution you'd like

An efficient API to map between CUDA/HIP IDs and parsec device IDs.

Describe alternatives you've considered

TTG currently implements this mapping but it requires us to find the first device ID and then add that to the CUDA/HIP ID to get the parsec ID. That seems brittle and would fail if we ever support multiple device types.

Additional context

Add any other context, references, and related works about the feature request here.

devreal avatar Jun 04 '24 13:06 devreal