Bidirectional - different bandwidth limits for the two transfer directions #1102
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
Catchup with laters iper3 changes
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.
Version of iperf3 (or development branch, such as
masteror3.1-STABLE) to which this pull request applies:3.9+
Issues fixed (if any):
Different bandwidth limits for two transfer directions #1093
Brief description of code changes (suitable for use as a commit message):
Suggested enhancement to allow different bandwidth limits for the two transfer directions in bidirectional test.
An optional distinct bitrate for the server is specified in sub-argument added to
--bidir.When specified, in bidirectional test
--bitrateis applicable only for the client.When not specified,
--bitratevalue is used also for the server, as in current functionality.