UCT/IB/MLX5/GDAKI: Added knob to control retaining inactive ctx.#11348
Open
rakhmets wants to merge 2 commits intoopenucx:masterfrom
Open
UCT/IB/MLX5/GDAKI: Added knob to control retaining inactive ctx.#11348rakhmets wants to merge 2 commits intoopenucx:masterfrom
rakhmets wants to merge 2 commits intoopenucx:masterfrom
Conversation
rakhmets
force-pushed
the
topic/gdaki-do-not-retain-inactive-ctx-2
branch
from
bdb5f74 to
518337c
Compare
rakhmets
force-pushed
the
topic/gdaki-do-not-retain-inactive-ctx-2
branch
from
518337c to
47d7345
Compare
rakhmets
force-pushed
the
topic/gdaki-do-not-retain-inactive-ctx-2
branch
from
8c54f9c to
9aea8e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Added
UCX_IB_GDA_RETAIN_INACTIVE_CTXknob to control retaining inactive CUDA primary device context atRC_GDAcomponent creation.Why?
It increases start up time if there is no active CUDA primary device context at
RC_GDAcomponent creation. As the context is required to check DMA_BUF and UAR support.It can also consume all the memory when running multiple processes on a system with a single GPU. As each process creates the context.