Skip to content

Allow user passed MTUs for ntttcp network perf tests. #3857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

SRIKKANTH
Copy link
Collaborator

There is a need for testing network perf with different MTU sizes.
This change enables it.

@LiliDeng LiliDeng requested a review from Copilot June 12, 2025 14:13
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enables users to pass custom MTU values for Ntttcp network performance tests.

  • Updated test functions in networkperf.py to accept an additional variables dictionary parameter.
  • Modified perf_ntttcp in common.py to extract and apply the MTU from the provided variables.
  • Updated Ntttcp performance message creation and dataclasses in ntttcp.py and messages.py to include client and server MTU fields.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
microsoft/testsuites/performance/networkperf.py Added variables parameter to test case functions for Ntttcp performance testing.
microsoft/testsuites/performance/common.py Introduced MTU extraction from variables and applied MTU settings for default and sriov NICs.
lisa/tools/ntttcp.py Updated performance message functions to include client and server MTU parameters.
lisa/messages.py Added MTU fields to the network performance message dataclasses.

@SRIKKANTH
Copy link
Collaborator Author

@LiliDeng please let me know if anything more needs to be done on this PR.

@squirrelsc
Copy link
Member

Please hold off on this change for now. We're currently adding a unified message for ntttcp. Once that's merged, please add the new metrics to the unified message.

#3863

@SRIKKANTH SRIKKANTH force-pushed the smyakam/custom_mtu_netperf/06_12_2025 branch from 0918e8d to 7783b9f Compare June 20, 2025 07:21
@squirrelsc
Copy link
Member

Please hold off on this change for now. We're currently adding a unified message for ntttcp. Once that's merged, please add the new metrics to the unified message.

#3863

#3863 is merged, please update the PR to enable mtu for unified ntttcp messages too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants