Repository navigation
feat(net): check DPDK startup memory headroom - #23
Merged
Merged
Conversation
Estimate remaining netvsc event/RNDIS and mlx5 cache allocations from the fixed topology. Check each populated EAL heap and its largest free block, and report host hugepages separately for diagnostics. The startup API does not initialize EAL or reserve runtime memory. Validation: 10 budget/sysfs tests, 8 startup scenarios using a real ring PMD with heap fault injection, and 8 existing adaptive network tests pass. No physical NIC test.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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
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.
Add a startup check for DPDK memory remaining after application allocations, including SPDK when enabled. Applications call
DpdkBackend::CheckMemoryBudget()before publishing readiness.The check budgets netvsc VMBus growth/RNDIS scratch and mlx5 lookup-cache growth, plus allocator headroom. Each populated NUMA heap must satisfy the remaining-byte and largest-block requirements. Failures report the deficit; host hugepage counts are logged separately and never counted as acquired capacity. Kernel networking skips the check.
This is a conservative admission check for the fixed topology, not a memory reservation or a guarantee for hotplug or arbitrary fragmentation. DPDK sources are unchanged.
Validation
ctest --test-dir /tmp/bycorf-dpdk-budget-build -R 'DpdkMemory|HostHugepage|DpdkAdaptive' --output-on-failure