Skip to contentSkip to conversation

Reduce memory footprint by using rte_max_lcore instead of RTE_MAX_LCORE

wishes/any Bug 1905 [email protected] 1 participant 1 message Mar 20

lore
Share & tools
lore
#0 lore raw

http://bugs.dpdk.org/show_bug.cgi?id=1905

Bug ID: 1905
Summary: Reduce memory footprint by using rte_max_lcore instead
of RTE_MAX_LCORE
Product: wishes
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: any
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Group: wishes-managers

Goal:
Reduce memory footprint of DPDK applications

Means:
Many arrays are sized to RTE_MAX_LCORE, which is set at build time. This affects the memory footprint when RTE_MAX_LCORE is significantly higher than the number of lcores used by the application.

Let's introduce an application startup-time configuration variable, rte_max_lcore, to serve the same purposes RTE_MAX_LCORE does today. It should be an optional EAL parameter, using RTE_MAX_LCORE as default.

By rightsizing the arrays scaling with the number of lcores, the application memory footprint would be reduced, and allow building DPDK with a huge RTE_MAX_LCORE.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.