[dpdk-dev] [PATCH] mk: link ring mempool by default for app build
shreyansh.jain at nxp.com
Tue Apr 18 14:25:49 CEST 2017
> -----Original Message-----
> From: Olivier MATZ [mailto:olivier.matz at 6wind.com]
> Sent: Tuesday, April 18, 2017 5:34 PM
> To: Shreyansh Jain <shreyansh.jain at nxp.com>
> Cc: dev at dpdk.org; thomas at monjalon.net; bruce.richardson at intel.com;
> john.miller at atomicrules.com
> Subject: Re: [PATCH] mk: link ring mempool by default for app build
> On Thu, 13 Apr 2017 14:32:07 +0530, Shreyansh Jain <shreyansh.jain at nxp.com>
> > Signed-off-by: Shreyansh Jain <shreyansh.jain at nxp.com>
> Fixes: 9a8e9b57f544 ("mempool: move ring handler as a driver")
> Acked-by: Olivier Matz <olivier.matz at 6wind.com>
> > ---
> > Context:
> > From the discussion in , it was observed that application should
> > have a default pool already linked even in case of shared builds.
> > Ring is especially important because packet mbuf creation API refer to
> > ring_mp_mc as default handler.
> > Documentation for this is pending.
> >  http://dpdk.org/ml/archives/dev/2017-April/063819.html
> Maybe this comment could go in the patch.
I can send another version of the patch with some part of the above documentation within the patch commit.
More information about the dev