UCT/TCP: Filtered out bridge devices. #9475
Merged
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
rakhmets
force-pushed
the
topic/tcp-no-bridges
branch
from
f0ae127 to
b6e1145
Compare
brminich
previously approved these changes
Nov 7, 2023
tvegas1
previously approved these changes
Nov 7, 2023
yosefe
reviewed
Nov 8, 2023
tvegas1
approved these changes
Nov 10, 2023
rakhmets
force-pushed
the
topic/tcp-no-bridges
branch
from
4d5d882 to
9e5f37d
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
Filtered out bridge devices.
Added control
UCX_TCP_BRIDGE_ENABLE. The default value is set tono. It means that the function querying the list of available TCP devices doesn't include bridge devices to the list.Why ?
The lane associated with the bridge device may be selected for transferring data. However, the lane is unreachable.