UCT/IB: Skip multi-thread memory registration for symmetric key #9447
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
brminich
previously approved these changes
Oct 26, 2023
tvegas1
force-pushed
the
smkey_without_mt_reg
branch
from
d1342d1
to
bf2be63
Compare
brminich
approved these changes
Oct 26, 2023
ivankochin
approved these changes
Oct 27, 2023
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s), but failed to run 1 pipeline(s). |
yosefe
approved these changes
Oct 27, 2023
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
Skip multi-threaded memory registration when symmetric key is requested and FW supports it.
Why ?
Simplest approach, could later be improved to generate KSM(MT) with specific mkey_index using KSM wrapper introduced by related #9424.
How ?
Add corresponding tests and assertion.