public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [wishes/any Bug 1913] Introduce RTE_EAL_INIT_PRIO() alternative to RTE_INIT_PRIO()
Date: Wed, 25 Mar 2026 10:08:46 +0000	[thread overview]
Message-ID: <bug-1913-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 1913
           Summary: Introduce RTE_EAL_INIT_PRIO() alternative to
                    RTE_INIT_PRIO()
           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

RTE_INIT_PRIO(func, prio) is a macro by which libraries and applications can
install a function to be called before application main().

I propose a similar macro, RTE_EAL_INIT_PRIO(func, prio), to install functions
to be called during different stages of rte_eal_init().

Example use cases:

1. Conceptually move the trace library out of the EAL library, so the trace
library is no longer a core library upon which the EAL library depends; instead
the trace library would depend on the EAL library.

2. Make lcore variables use DPDK memory.
If lcore variables were to use DPDK, it would also limit the use of the lcore
variable constructor macros (RTE_LCORE_VAR_INIT(), RTE_LCORE_VAR_INIT_SIZE(),
RTE_LCORE_VAR_INIT_SIZE_ALIGN()) to after DPDK memory has been initialized;
they can no longer be used by RTE_INIT()/RTE_INIT_PRIO() functions.
This is possible if the libraries/applications currently using
RTE_INIT()/RTE_INIT_PRIO() could use RTE_EAL_INIT_PRIO() instead.

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

                 reply	other threads:[~2026-03-25 10:08 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-1913-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox