On Thu, Dec 15, 2022 at 10:05 AM Morten Brørup <m...@smartsharesystems.com> wrote: > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand > > Sent: Monday, 6 July 2020 22.53 > > > > DPDK components and applications can have their say when a new lcore is > > initialized. For this, they can register a callback for initializing > > and > > releasing their private data. > > > > Signed-off-by: David Marchand <david.march...@redhat.com> > > --- > > David, > > Shouldn't these callbacks be called from the EAL threads too, e.g. from > eal_thread_loop()? > > I looks like they are only called from eal_lcore_non_eal_allocate(), which is > only called from rte_thread_register().
These should be called for already present lcores on callback registration. See rte_lcore_callback_register(). -- David Marchand
