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.
DPDK: Add symmetric_mp hotplug test #4348
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
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
DPDK: Add symmetric_mp hotplug test #4348
Changes from all commits
28d60468f184f0f0b8acf1e9ceadbc71a565374ff58e8b01fc3845e1File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR description notes this hotplug test will fail on DPDK versions below 26.07. As written, the test will still run against older DPDK sources and fail noisily. Consider adding an explicit version gate (skip with a clear message) or a runbook variable/requirement that ensures only compatible DPDK sources/branches enable this test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo in the test description: "symmetic" → "symmetric".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With
hotplug_times=40,run_dpdk_symmetric_mpwill loop many times and (per current implementation) starts a newping_asynceach iteration without any visible join/wait. This can create many concurrent ping processes during the stress run, increasing flakiness and resource pressure. Consider changing the runner to wait for each async ping to finish before starting the next iteration (or make the stress case use synchronous ping), and/or cap concurrent ping jobs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Timeout.start_with_timeout()passeskill_timeoutto GNUtimeout --kill-after, which is a grace period after the initial signal (not an overall timeout). Setting it totest_timeout + 5can make hung symmetric_mp runs wait an extra ~minutes (e.g., 40-hotplug stress) before being force-killed. Consider using a small, fixed grace period (e.g., 30–60s) independent oftest_timeout.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same
kill_timeoutissue as the primary process:--kill-afteris a post-signal grace period, so tying it totest_timeoutcan significantly extend worst-case hangs. Use a small fixed grace period here as well.Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change makes
switch_srioveffectively blocking on the Azure NIC update every time because it unconditionally callspoller.result(). In this PR, call sites explicitly passwait=False(e.g., the hotplug test), so this likely breaks the intended non-wait semantics and can significantly slow down hotplug loops. Consider honoring thewaitparameter: only callpoller.result()(and any subsequent state assertions) whenwait=True; otherwise return after starting the update (or return the poller for the caller to await).Uh oh!
There was an error while loading. Please reload this page.