[dpdk-dev] [PATCH 2/2 v3] kni: add documentation for the mempool capacity

Alex Wang alex at awakenetworks.com
Thu Jun 9 19:06:59 CEST 2016


Just to confirm, should I do anything before it gets merged?

On Thu, Jun 9, 2016 at 5:03 AM, Mcnamara, John <john.mcnamara at intel.com>
wrote:

> > -----Original Message-----
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Alex Wang
> > Sent: Saturday, May 21, 2016 8:59 AM
> > To: dev at dpdk.org
> > Cc: Yigit, Ferruh <ferruh.yigit at intel.com>; Alex Wang
> > <alex at awakenetworks.com>
> > Subject: [dpdk-dev] [PATCH 2/2 v3] kni: add documentation for the mempool
> > capacity
> >
> > From: Alex Wang <alex at awakenetworks.com>
> >
> > Function like 'rte_kni_rx_burst()' keeps allocating 'MAX_MBUF_BURST_NUM'
> > mbufs to kni fifo queue unless the queue's capacity
> > ('KNI_FIFO_COUNT_MAX') is reached.  So, if the mempool is under-
> > provisioned, user may run into "Out of Memory" logs from KNI code.
> > This commit documents the need to provision mempool capacity of more than
> > "2 x KNI_FIFO_COUNT_MAX" for each KNI interface.
> >
> > Signed-off-by: Alex Wang <alex at awakenetworks.com>
> > Acked-by: Ferruh Yigit <ferruh.yigit at intel.com>
>
> Acked-by: John McNamara <john.mcnamara at intel.com>
>
>


More information about the dev mailing list