All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [wishes/any Bug 1905] Reduce memory footprint by using rte_max_lcore instead of RTE_MAX_LCORE
Date: Fri, 20 Mar 2026 11:13:28 +0000	[thread overview]
Message-ID: <bug-1905-3@http.bugs.dpdk.org/> (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: 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.

                 reply	other threads:[~2026-03-20 11:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1905-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.