[dpdk-dev] [PATCH 0/2] Multiple Pktmbuf mempool support
hemant.agrawal at nxp.com
Fri Sep 22 09:13:36 CEST 2017
Any opinion on this patchset?
On 7/4/2017 5:52 PM, Hemant Agrawal wrote:
> This patch is in addition to the patch series submitted by
> Santosh to allow application to set mempool handle.
> The existing pktmbuf pool create api only support the internal use
> of "CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS", which assumes that the HW
> can only support one type of mempool for packet mbuf.
> There are multiple additional requirements.
> 1. The platform independent image detects the underlying bus,
> based on the bus and resource detected, it will dynamically select
> the default mempool. This need not to have the application knowlege.
> e.g. DPAA2 and DPAA are two different NXP platforms, based on the
> underlying platform the default ops for mbuf can be dpaa or dpaa2.
> Application should work seemlessly whether it is running on dpaa or dpaa2.
> 2.Platform support more than one type of mempool for pktmbuf,
> depend on the availability of resource, the driver can decide one
> of the mempool for the current packet mbuf request.
> 3. In case of where application is providing the mempool, as proposed
> in , the check preference logic will be bypassed and application
> config will take priority.
> Allow application set mempool handle
> Hemant Agrawal (2):
> mempool: check the support for the given mempool
> mbuf: add support for preferred mempool list
> config/common_base | 2 ++
> lib/librte_mbuf/rte_mbuf.c | 28 +++++++++++++++++++++++-----
> lib/librte_mempool/rte_mempool.h | 24 ++++++++++++++++++++++++
> lib/librte_mempool/rte_mempool_ops.c | 32 ++++++++++++++++++++++++++++++++
> 4 files changed, 81 insertions(+), 5 deletions(-)
More information about the dev