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_PREFERRED_CLUSTER_DIMENSION in LaunchConfig #2661
Is your feature request related to a problem? Please describe.
LaunchConfig does not expose CU_LAUNCH_ATTRIBUTE_PREFERRED_CLUSTER_DIMENSION, which sets preferred thread-block cluster dimensions for a launch (preferred size must be a multiple of the minimum cluster dimension).
Users can set CU_LAUNCH_ATTRIBUTE_PREFERRED_CLUSTER_DIMENSION via LaunchConfig.
Mapping to the native launch attribute is tested.
Describe alternatives you've considered
Use cuda.bindings.driver (CUlaunchAttribute / CU_LAUNCH_ATTRIBUTE_PREFERRED_CLUSTER_DIMENSION) 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.
Activity
launch_attrinLaunchConfigctor #496