On Fri, 17 Mar 2017 17:12:59 +0000, Hemant Agrawal <hemant.agra...@nxp.com> wrote: > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas.monja...@6wind.com] > > Sent: Friday, March 17, 2017 7:13 PM > > To: Hemant Agrawal <hemant.agra...@nxp.com> > > Cc: dev@dpdk.org; olivier.m...@6wind.com; Shreyansh Jain > > <shreyansh.j...@nxp.com>; ferruh.yi...@intel.com > > Subject: Re: [PATCH v1] NXP DPAA2 External Mempool Driver > > > > 2017-03-17 18:17, Hemant Agrawal: > > > (This patches has been split from DPAA2 PMD v8 series [1] as per > > > comments received on ML [2].) > > > > > > This patch implements the HW mempool offload driver for packets > > > buffers using the FSLMC provided DPBP object. > > > > > > The new pool is being configured using compile time option and pool > > > name as "dpaa2". > > > > > > Dependency: > > > This patchset is based on "NXP DPAA2 FSLMC Bus Driver" patchset [3]. > > > > > > References: > > > [1] http://dpdk.org/ml/archives/dev/2017-March/059000.html > > > [2] http://dpdk.org/ml/archives/dev/2017-March/059789.html > > > [3] http://dpdk.org/ml/archives/dev/2017-March/060453.html > > > > I'm sorry, I think there is misunderstanding. > > We were saying that you should move the existing mempool handlers first. > > Have you submitted a patch for the ring and stack mempool handlers? > [Hemant] > > I will do it. But that work is independent of NXP patches? Isn't it?
I'd say the existing handlers have to be moved first, to avoid to have a state where there are handlers at 2 different locations. So to me, it's just a chronological dependency. Regards, Olivier
