Starting trace module using a broadcast network for XDP Client #8455
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
Trace modules are being started at different times. Because of this, trace start can't be used to verify timer synchronization.
How problem was solved, alternative solutions (if any) and why they were rejected
A broadcast network is used to start the trace modules. Alternative solution is to start trace module using true event sequentially. But the differences between timers of trace modules will be hundreds of cylces. With broadcast network, the difference is too less.
What has been tested and how, request additional testing if necessary
On client I have verified one model. The timers were in sync and trace module starts with broadcast event.