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

2016-06-09 Thread Alex Wang
Just to confirm, should I do anything before it gets merged? On Thu, Jun 9, 2016 at 5:03 AM, Mcnamara, John 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 a

[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

[dpdk-dev] [PATCH 1/2] rte_kni: Fix documentation.

2016-05-23 Thread ALeX Wang
Sorry for the delayed reply, just sent V2~ On 18 May 2016 at 03:33, Ferruh Yigit wrote: > On 5/14/2016 7:22 PM, Alex Wang wrote: > > From: Alex Wang > > > > The 'mbufs' alloc/free descriptions for 'rte_kni_tx_burst()' > > and 'rte_kni_rx_burst()' should be inverted.

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

2016-05-21 Thread Alex Wang
From: Alex Wang <a...@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" lo

[dpdk-dev] [PATCH 1/2 v3] kni: fix inverted function comments

2016-05-21 Thread Alex Wang
From: Alex Wang <a...@awakenetworks.com> The 'mbufs' alloc/free descriptions for 'rte_kni_tx_burst()' and 'rte_kni_rx_burst()' should be inverted. Fixes: 3fc5ca2 (kni: initial import) Signed-off-by: Alex Wang Acked-by: Ferruh Yigit --- lib/librte_kni/rte_kni.h | 8 1 file chan

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

2016-05-21 Thread Alex Wang
From: Alex Wang <a...@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" lo

[dpdk-dev] [PATCH 1/2 v2] kni: fix inverted function comments

2016-05-21 Thread Alex Wang
From: Alex Wang <a...@awakenetworks.com> The 'mbufs' alloc/free descriptions for 'rte_kni_tx_burst()' and 'rte_kni_rx_burst()' should be inverted. Fixes: 3fc5ca2 (kni: initial import) Signed-off-by: Alex Wang --- lib/librte_kni/rte_kni.h | 8 1 file changed, 4 insertions

[dpdk-dev] possible kni bug and proposed fix

2016-05-17 Thread ALeX Wang
On 17 May 2016 at 03:07, Ferruh Yigit wrote: > On 5/16/2016 4:31 PM, ALeX Wang wrote: > > Hi Ferruh, > > > > Thx for pointing out the 'fill alloc_q with these mubfs _until it gets > > full_.', > > > > I saw the size of all queues are 'KNI_FIFO_COUNT_MAX

[dpdk-dev] possible kni bug and proposed fix

2016-05-16 Thread ALeX Wang
#a0cdd727cdc227d005fef22c0189f3dfe 'rte_kni_rx_burst' does the 'It handles allocating the mbufs for KNI interface alloc queue.' Thanks, Alex Wang, On 16 May 2016 at 04:20, Ferruh Yigit wrote: > On 5/15/2016 5:48 AM, ALeX Wang wrote: > > Hi, > > > > When using the kni module to test

[dpdk-dev] possible kni bug and proposed fix

2016-05-14 Thread ALeX Wang
)) { /* Out of memory */ Thanks, -- Alex Wang,

[dpdk-dev] [PATCH 2/2] rte_kni: Add documentation for the mempool capacity.

2016-05-14 Thread Alex Wang
From: Alex Wang <a...@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" lo

[dpdk-dev] [PATCH 1/2] rte_kni: Fix documentation.

2016-05-14 Thread Alex Wang
From: Alex Wang <a...@awakenetworks.com> The 'mbufs' alloc/free descriptions for 'rte_kni_tx_burst()' and 'rte_kni_rx_burst()' should be inverted. Signed-off-by: Alex Wang --- lib/librte_kni/rte_kni.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/libr

[dpdk-dev] [4.4 kernel] kni lockup, kernel dump

2016-04-14 Thread ALeX Wang
Thx, Ferruh and Thomas for the confirmation and pointer! On 14 April 2016 at 07:43, Thomas Monjalon wrote: > 2016-04-14 15:29, Ferruh Yigit: > > On 4/13/2016 11:26 PM, ALeX Wang wrote: > > > Did more experiment, found that it has nothing to do with the kernel > > > v

[dpdk-dev] [4.4 kernel] kni lockup, kernel dump

2016-04-13 Thread ALeX Wang
Did more experiment, found that it has nothing to do with the kernel version, It only happens when using kni module with '--no-huge' eal flag... Is that expected? Thanks, Alex Wang, On 12 April 2016 at 17:28, ALeX Wang wrote: > I tried compiling both dpdk-2.2 and dpdk-16.04, all h

[dpdk-dev] [4.4 kernel] kni lockup, kernel dump

2016-04-12 Thread ALeX Wang
I tried compiling both dpdk-2.2 and dpdk-16.04, all have the issue, Thanks, On 12 April 2016 at 17:19, ALeX Wang wrote: > Hi, > > I recently upgraded my debian/jessie to 4.4 kernel, and my application > uses kni to > create test interface, > > However, when doing 'rte_kni

[dpdk-dev] [4.4 kernel] kni lockup, kernel dump

2016-04-12 Thread ALeX Wang
0bcb88 [ 888.146705] ---[ end trace ef3848430517129b ]--- -- Alex Wang,

[dpdk-dev] Must kni be associated with a dpdk port?

2016-03-31 Thread ALeX Wang
Thx a lot, for the answer,! Exactly what I'm looking for,~ On 31 March 2016 at 02:55, Ferruh Yigit wrote: > On 3/30/2016 6:20 PM, ALeX Wang wrote: > > Hi, > > > > I want to use 'rte_kni_alloc()' to create a kernel iface and > > use it to test application rx

[dpdk-dev] Must kni be associated with a dpdk port?

2016-03-30 Thread ALeX Wang
with a dpdk port? Thanks, -- Alex Wang,