[XDP] Use stream ID and Master or Slave information for each interface tile from metadata #8743
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
Signed-off-by: Vinod Pangul <[email protected]>
jvillarre
approved these changes
Feb 7, 2025
pgschuey
approved these changes
Feb 7, 2025
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.
Problem solved by the commit
[CR-1222671] : As described in the CR, In some cases, incorrect ports were getting configured and reported incorrectly. This was resulting into empty trace data even for applicable ports.
Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered
[CR-1222671]
How problem was solved, alternative solutions (if any) and why they were rejected
Now Client uses, mapping of tile and its mapping of all applicable streamIds and Ports. This change makes it same as Edge usage of ports and streamIds and completely metadata driven.
Risks (if any) associated the changes in the commit
Low
What has been tested and how, request additional testing if necessary
Verified on Client
Documentation impact (if any)