Update expected result for ovs bridge throughput #6090
Closed
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
Per bug https://issues.redhat.com/browse/RHEL-53963, the expected result is changed. Signed-off-by: Yalan Zhang <[email protected]>
|
@yalzhang can you plz upload test results? |
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.
For ovs bridge, if we set differnet value for peak and average, the average will map to the min rate, and peak to the max rate, which is different with linux bridge. For linux bridge, the average will map to max rate. To make the behavior consistent, set peak and average to be the same. When we set different value for average and peak on ovs bridge, libvirt will report warning on the libvirtd log.