Skip to content

UCT/IB/MLX5/GDAKI: Fixed retaining inactive primary context.#11276

Draft
rakhmets wants to merge 1 commit intoopenucx:masterfrom
rakhmets:topic/gdaki-do-not-retain-inactive-ctx
Draft

UCT/IB/MLX5/GDAKI: Fixed retaining inactive primary context.#11276
rakhmets wants to merge 1 commit intoopenucx:masterfrom
rakhmets:topic/gdaki-do-not-retain-inactive-ctx

Conversation

@rakhmets
Copy link
Copy Markdown
Contributor

What?

Fixed retaining inactive primary context.

Why?

Without checking the status of the primary CUDA context on the device, a context can be created on an unused device by calling cuDevicePrimaryCtxRetain. And it will be retained until the cuDevicePrimaryCtxRelease call is made by UCS_CLASS_CLEANUP_FUNC(uct_rc_gdaki_iface_t).

@rakhmets rakhmets force-pushed the topic/gdaki-do-not-retain-inactive-ctx branch from ffd9d7f to e3f2ba7 Compare March 19, 2026 15:26
@rakhmets rakhmets force-pushed the topic/gdaki-do-not-retain-inactive-ctx branch from e3f2ba7 to a598cb4 Compare March 23, 2026 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant