[dpdk-dev] Bond port with multiple queues

2015-12-02 Thread Sergey Balabanov
get all packets from the slave port #0 on some queue and all packets from the slave port #1 on another queue. Does anybody know is there a way to configure bond port in a way when all traffic on port #0 goes to queue #0 and traffic on port #1 goes to queue #1? Thanks, Sergey Balabanov

[dpdk-dev] [PATCH] kni: set kni mac on ioctl_create

2015-08-28 Thread Sergey Balabanov
Hi, Probably I missed something in understanding why the mac is not set on kni creation. Any comments would be highly appreciated. Thanks, Sergey On Friday 28 August 2015 16:06:27 Sergey Balabanov wrote: > There is a situation when ioctl returns zero mac address (00:00:00:00:00:00) > fo

[dpdk-dev] [PATCH] kni: set kni mac on ioctl_create

2015-08-28 Thread Sergey Balabanov
There is a situation when ioctl returns zero mac address (00:00:00:00:00:00) for just created kni. The situation happens because kni mac is set on 'ipconfig up' event (kni_net_open callback) not on kni creation (kni_ioctl_create). Signed-off-by: Sergey Balabanov --- lib/librte_eal/li

[dpdk-dev] [PATCH] mbuf: fix incompatibility with C++ in header file

2015-08-14 Thread Sergey Balabanov
The patch duplicates http://dpdk.org/dev/patchwork/patch/6750/ On Friday 14 August 2015 11:33:15 Avi Kivity wrote: > C++ doesn't allow implied casting from void * to another pointer, so > supply an explicit cast. > > Signed-off-by: Avi Kivity > --- > lib/librte_mbuf/rte_mbuf.h | 2 +- > 1 file

[dpdk-dev] [PATCH] mbuf & mempool: explicit typecast on function return

2015-08-12 Thread Sergey Balabanov
When DPDK is being compiled in C++ project using g++ then 'invalid conversion from' error appears. Added explicit typecast on function return to get rid of the error. Signed-off-by: Sergey Balabanov --- lib/librte_mbuf/rte_mbuf.h | 2 +- lib/librte_mempool/rte_mempool.h | 4 ++-

[dpdk-dev] [PATCH v2] bonding: 8023ad: fix incorrect typecast of socket

2015-08-07 Thread Sergey Balabanov
On slave activation in LACP (8023AD) SOCKET_ANY_ID (which is -1) is being casted to unsigned char and then to signed int. The result is that socket_id has value of 255, not -1. This results to memory allocation failure. Signed-off-by: Sergey Balabanov --- drivers/net/bonding

[dpdk-dev] [PATCH] bonding: 8023ad: fix incorrect typecast of socket

2015-08-05 Thread Sergey Balabanov
On slave activation in LACP (8023AD) SOCKET_ANY_ID (which is -1) is being casted to unsigned char and then to signed int. The result is that socket_id has value of 255, not -1. This results to memory allocation failure. --- drivers/net/bonding/rte_eth_bond_8023ad.c | 2 +- 1 file changed, 1 insert