> From: David Marchand [mailto:david.march...@redhat.com]
> Sent: Friday, 16 December 2022 09.09
>
> Morten,
>
> On Thu, Dec 15, 2022 at 11:21 AM Morten Brørup
> wrote:
> > > > Shouldn't these callbacks be called from the EAL threads too,
> e.g.
> > > from eal_thread_loop()?
> > > >
> > > > I lo
Morten,
On Thu, Dec 15, 2022 at 11:21 AM Morten Brørup
wrote:
> > > 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().
+CC Mattias, I forgot to put you on this discussion
> From: David Marchand [mailto:david.march...@redhat.com]
> Sent: Thursday, 15 December 2022 10.09
llbacks
>
> On Thu, Dec 15, 2022 at 10:05 AM Morten Brørup
> wrote:
> >
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of David Marchand
On Thu, Dec 15, 2022 at 10:05 AM Morten Brørup
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 callba
> 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.
>
> Sign
5 matches
Mail list logo
