[PATCH] dumpcap: fix mbuf pool ring type
Morten Brørup
mb at smartsharesystems.com
Tue Nov 7 18:38:32 CET 2023
> From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> Sent: Tuesday, 7 November 2023 17.41
>
> On Tue, 7 Nov 2023 08:22:37 +0100
> Morten Brørup <mb at smartsharesystems.com> wrote:
>
> > > >
> > > > Or are you saying that if they want to use dumpcap, they must
> choose
> > > a thread safe pool type for their application (regardless if the
> > > application is single-threaded or not)?
> > >
> > > There is no command line of EAL nature in dumpcap.
> > > This is intentional.
> > > QED: overriding default pool type is not going to be a possible
> >
> > The preferred mbuf pool type can configured in the primary process by
> EAL params. If so configured, it is stored in a memzone named
> "mbuf_user_pool_ops".
> > And if it is set there, the secondary process will also use it as its
> preferred mbuf pool type.
>
> If user decides to use a thread unsafe mempool, wouldn't it break in
> every PMD as well.
Yes, except if the application only uses one thread for packet processing. Then thread safety is not necessary.
More information about the dev
mailing list