Refactor: Rename networking-dpdk-cpu-pinning-exec-probe to performanc… #3320
Conversation
This file contains hidden or 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
…e-cpu-pinning-no-exec-probes - Renamed test from networking-dpdk-cpu-pinning-exec-probe to performance-cpu-pinning-no-exec-probes - Moved test from networking suite to performance suite - Removed DPDK-specific filtering (filterDPDKRunningPods) - Now checks ALL Guaranteed QoS pods with exclusive CPUs (broader coverage) - Updated test descriptions, remediation, and documentation - Cleaned up unused helper functions and imports
Collaborator
|
from change #3320: |
greyerof
approved these changes
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Renamed and refactored the test case networking-dpdk-cpu-pinning-exec-probe to performance-cpu-pinning-no-exec-probes. The test has been moved from the networking suite to the performance suite and now checks ALL pods with CPU pinning (Guaranteed QoS with exclusive CPUs), not just DPDK-specific workloads.
Rename and Move Test Case ✅
Old identifier: networking-dpdk-cpu-pinning-exec-probe
New identifier: performance-cpu-pinning-no-exec-probes
Old suite: networking
New suite: performance
Full test name: performance-cpu-pinning-no-exec-probes
Remove DPDK-Specific Filtering ✅
Removed filterDPDKRunningPods() function that checked for vfio-pci driver
Removed GetCPUPinningPodsWithDpdk() helper function
Test now checks ALL Guaranteed QoS pods with exclusive CPUs
Broader coverage: protects DPDK workloads AND other latency-sensitive workloads