Introduce RTE_EAL_INIT_PRIO() alternative to RTE_INIT_PRIO()

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: [email protected]
          Reporter: [email protected]

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.