public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
* [wishes/any Bug 1905] Reduce memory footprint by using rte_max_lcore instead of RTE_MAX_LCORE
@ 2026-03-20 11:13 bugzilla
  0 siblings, 0 replies; only message in thread
From: bugzilla @ 2026-03-20 11:13 UTC (permalink / raw)
  To: dev

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: dev@dpdk.org
          Reporter: mb@smartsharesystems.com
  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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2026-03-20 11:13 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-20 11:13 [wishes/any Bug 1905] Reduce memory footprint by using rte_max_lcore instead of RTE_MAX_LCORE bugzilla

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox