[dpdk-dev] possible kni bug and proposed fix

2016-05-17 Thread Ferruh Yigit
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 (1024)'... > The corresponding memory required is more than what I specify as > 'socket_mem' (since i'

[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 (1024)'... > > The corresponding memory req

[dpdk-dev] possible kni bug and proposed fix

2016-05-16 Thread Ferruh Yigit
On 5/15/2016 5:48 AM, ALeX Wang wrote: > Hi, > > When using the kni module to test my application inside > debian (virtualbox) VM (kernel version 4.4), I get the > > "KNI: Out of memory" > > from syslog every time I `tcpreply` packets through > the kni interface. > > After checking source code,

[dpdk-dev] possible kni bug and proposed fix

2016-05-16 Thread ALeX Wang
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 (1024)'... The corresponding memory required is more than what I specify as 'socket_mem' (since i'm using VM)... Also, in my use case, I only `tcpreplay

[dpdk-dev] possible kni bug and proposed fix

2016-05-14 Thread ALeX Wang
Hi, When using the kni module to test my application inside debian (virtualbox) VM (kernel version 4.4), I get the "KNI: Out of memory" from syslog every time I `tcpreply` packets through the kni interface. After checking source code, I saw that when I call 'rte_kni_rx_burst()', no matter how m