You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEA]: Support CU_LAUNCH_ATTRIBUTE_PRIORITY in LaunchConfig #2631
Users can set CU_LAUNCH_ATTRIBUTE_PRIORITY via LaunchConfig.
Mapping to the native launch attribute is tested.
Describe alternatives you've considered
Use cuda.bindings.driver (CUlaunchAttribute / CU_LAUNCH_ATTRIBUTE_PRIORITY) and cuLaunchKernelEx directly.
Downside: leaves cuda.core users without a first-class LaunchConfig API; they must drop to low-level bindings, manage the attribute array themselves, and lose consistency with other LaunchConfig launch attributes (is_cooperative, programmatic_stream_serialization, etc.).
Additional context
Incremental LaunchConfig attribute coverage under #496 (same approach as #1334 for programmatic_stream_serialization).
No example code in the design notes for this attribute.
changed the title [-][FEA]: Add support for CU_LAUNCH_ATTRIBUTE_PRIORITY in LaunchConfig[/-][+][FEA]: Support CU_LAUNCH_ATTRIBUTE_PRIORITY in LaunchConfig[/+]on Aug 18, 2026
The goal is to expose CUDA's per-kernel launch priority through cuda.core.LaunchConfig, avoiding the need for users to construct CUlaunchAttribute manually with cuda.bindings.
We can add an optional priority field to LaunchConfig, declaring its Cython storage in _launch_config.pyd, and maping supplied values to CU_LAUNCH_ATTRIBUTE_PRIORITY and CUlaunchAttributeValue.priority in both native-conversion paths in _launch_config.pyx. Preserve the distinction between omitted priority and explicit priority=0.
Hi @ichensun I am on the same page that cuda.core.LaunchConfig is for when users don't set CUlaunchAttribute manually.
Adding a priority field and implementation plan in cython layer look good. Please also add test cases about setter/getter and/or explore if it is possible to test a policy at runtime (looks complicated can be in a separate PR).
Activity
launch_attrinLaunchConfigctor #496[-][FEA]: Add support for CU_LAUNCH_ATTRIBUTE_PRIORITY in LaunchConfig[/-][+][FEA]: Support CU_LAUNCH_ATTRIBUTE_PRIORITY in LaunchConfig[/+]ichensun commentedon Aug 25, 2026
The goal is to expose CUDA's per-kernel launch priority through
cuda.core.LaunchConfig, avoiding the need for users to constructCUlaunchAttributemanually withcuda.bindings.We can add an optional
priorityfield toLaunchConfig, declaring its Cython storage in_launch_config.pyd, and maping supplied values toCU_LAUNCH_ATTRIBUTE_PRIORITYandCUlaunchAttributeValue.priorityin both native-conversion paths in_launch_config.pyx. Preserve the distinction between omitted priority and explicitpriority=0.lijinf2 commentedon Aug 25, 2026
Hi @ichensun I am on the same page that cuda.core.LaunchConfig is for when users don't set CUlaunchAttribute manually.
Adding a
priorityfield and implementation plan in cython layer look good. Please also add test cases about setter/getter and/or explore if it is possible to test a policy at runtime (looks complicated can be in a separate PR).