UCP/RNDV/RCACHE: Don't use rcache for RNDV frag mpool #10309
+31
−14
Conversation
This file contains 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
yosefe
reviewed
Nov 20, 2024
brminich
approved these changes
Nov 22, 2024
yosefe
approved these changes
Nov 24, 2024
iyastreb
force-pushed
the
ucp-rndv-frag-mpool-no-rcache
branch
from
de9647e
to
3fe3e0f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This is an auxiliary PR to introduce new invalidation design in UCX. The aim is to avoid using rcache for RNDV fragment memory pool
Why?
RNDV fragment memory pool is created on demand and remains allocated during the application lifetime. Rcache is desirable for this use case, because:
How?
Introduce new UCP memh flag NO_RCACHE