[dpdk-dev] [PATCH 2/2 v2] kni: Add documentation for the mempool capacity

2016-05-23 Thread Ferruh Yigit
On 5/23/2016 6:00 PM, Ferruh Yigit wrote: > On 5/21/2016 8:25 AM, Alex Wang wrote: >> From: Alex Wang >> >> 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 mempoo

[dpdk-dev] [PATCH 2/2 v2] kni: Add documentation for the mempool capacity

2016-05-23 Thread Ferruh Yigit
On 5/21/2016 8:25 AM, Alex Wang wrote: > From: Alex Wang > > 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 o

[dpdk-dev] [PATCH 2/2 v2] kni: Add documentation for the mempool capacity

2016-05-23 Thread Alex Wang
Sht, sorry for missing that, sending V3, On Mon, May 23, 2016 at 10:10 AM, Ferruh Yigit wrote: > On 5/23/2016 6:00 PM, Ferruh Yigit wrote: > > On 5/21/2016 8:25 AM, Alex Wang wrote: > >> From: Alex Wang > >> > >> Function like 'rte_kni_rx_burst()' keeps > >> allocating 'MAX_MBUF_BURST_NUM'

[dpdk-dev] [PATCH 2/2 v2] kni: Add documentation for the mempool capacity

2016-05-21 Thread Alex Wang
From: Alex Wang 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