Add mutli-CPU Affinity option support for Linux (not for FreeBSD) #1778
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
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:master
Issues fixed (if any): Support affinity/pinning of parallel flows to different CPUs #1738
Brief description of code changes (suitable for use as a commit message):
Suggested support for multi-CPU Affinity option on Linux. The PR is only for Linux, since I don't have FreeBSD machine.
The format of a CPUs list is using
/as a separator ("n1/n1/...") since,is already used to separate between the client and server CPUs lists.The fix is backward compatible, passing the CPUs list to the server in a new "server_cpu_set" JSON item and passing the first CPU defined in the server's list in the legacy "server_affinity" item.