CUDA component support for (1) various Compute Capabilities and (2) multiple GPU configurations #297
Labels
component-cuda
PRs and Issues related to the cuda component
priority-high
PRs and Issues that are of high priority
Expected behaviors for PAPI CUDA component for:
1. Systems with single GPU configurations:
1.1 - A100 (CC 8.0) requires Perfworks API; does not work with legacy Event API.
1.2 - P100 (CC 6.0) does not work with Perfworks API; requires legacy Event API.
1.3 - V100 (CC 7.0) works with either Perfworks API or Event API.
2. Systems with multiple GPU configurations:
2.1 - Monitoring events for both A100 and V100 should work fine in PAPI if Perfworks API is used.
papi_component_avail
output could say something like:Name: cuda CUDA profiling via NVIDIA CuPTI interfaces
\-> Partially disabled: System includes multiple compute capabilities: <7.0, =7.0, >7.0.
Only support for CC <=7.0 enabled.
2.2 - Monitoring events for both P100 and V100 should work fine in PAPI if Legacy Event API is used.
papi_component_avail
output could say something like:Name: cuda CUDA profiling via NVIDIA CuPTI interfaces
\-> Partially disabled: System includes multiple compute capabilities: <7.0, =7.0, >7.0.
Only support for CC >=7.0 enabled.
2.3 - Monitoring events for both A100 and P100 is not expected to work.
If Legacy Event API is enabled, then PAPI CUDA should support monitoring for P100 (and V100) but not A100.
In that case, the
papi_component_avail
output could say something like:Name: cuda CUDA profiling via NVIDIA CuPTI interfaces
\-> Partially disabled: System includes multiple compute capabilities: <7.0, =7.0, >7.0.
Only support for CC <=7.0 enabled.
If Perfworks API is enabled, then PAPI CUDA should support monitoring for A100 (and V100) but not P100.
In that case, the
papi_component_avail
output could say something like:Name: cuda CUDA profiling via NVIDIA CuPTI interfaces
\-> Partially disabled: System includes multiple compute capabilities: <7.0, =7.0, >7.0.
Only support for CC >=7.0 enabled.
The text was updated successfully, but these errors were encountered: