Perform CPU pinning for ntttcp if more than one numa nodes #3350
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
LiliDeng
approved these changes
Jul 16, 2024
kanchansenlaskar
deleted the
kasenlaskar/check_numa_node_set_cpu_affinity
branch
r-dailey
pushed a commit
to r-dailey/lisa
that referenced
this pull request
Jul 24, 2024
r-dailey
pushed a commit
to r-dailey/lisa
that referenced
this pull request
Jul 24, 2024
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.
In order to have higher network performance numbers, it is important to have cpu pinning done for executing ntttcp command. This change is tested with both VM with multiple NUMA nodes and single NUMA node.