kni: describe mempool capacity requirement
authorAlex Wang <alex@awakenetworks.com>
Sat, 21 May 2016 07:58:36 +0000 (00:58 -0700)
committerThomas Monjalon <thomas.monjalon@6wind.com>
Tue, 14 Jun 2016 15:15:01 +0000 (17:15 +0200)
commit460860100017a96117564c5b59c9f241083f7f8a
tree0b773a0a5bfeb3573aabdc827cf0980c837e1032
parent1afa3d7ca6cc5ab8f0f8a95187b66c2f735f0682
kni: describe mempool capacity requirement

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@awakenetworks.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
lib/librte_kni/rte_kni.h