Re: [dpdk-users] Possibly wrong RX statistics reported by virtio driver (TRex generator)

2018-10-31 Thread Stephen Hemminger
On Wed, 31 Oct 2018 10:29:38 +0200 "Nikos Anastopoulos" wrote: > Hi list, > > > > The TRex traffic generator's folks recommended us to contact you for an issue > that might relate to DPDK virtio driver > (https://groups.google.com/forum/#!topic/trex-tgn/LxtTV7G43AE). > > > >

Re: [dpdk-users] Ideal design to use ip-fragmentation using multiple lcores

2018-10-31 Thread Stephen Hemminger
On Tue, 30 Oct 2018 18:55:02 -0700 Sungho Hong wrote: > Hello DPDK experts, > > I have a question of how to ideally use ip fragmentation and assemble using > N number of logical cores each associated with tx queues. > > Should the ip fragmentation table be single received by a single rx-queue?

[dpdk-users] Not able to receive packet via api rte_eth_rx_burst

2018-10-31 Thread Avinash Chaurasia
I have modified rxtx_callback example to just receive on single port. However it is not working rte_eth_stats_get() shows packets are present in ethernet ring via the field ipackets but rte_eth_rx_burst is not returning any packets. Code is included here, please let me know what I am doing wrong.

[dpdk-users] Bring DPDK on ConnectX-3

2018-10-31 Thread zzqq2199
Hi, Recently I have worked on running dpdk on our infiniband card but failed. Our adapters card is ConnectX-3, which is in the dpdk’s support hardwares list, but specific type, MSX6710-FS2F2 is not found in detailed support nics list of mlx4. Environment Adapter card: Mellanox MSX6710-FS2F2

Re: [dpdk-users] Failed to allocate tx pool

2018-10-31 Thread Raghu Gangi
Hi Cliff, Yes, I had tried it. When I set memory on both NUMA nodes it works without this issue. I set using the following commands: root@rg2-14053:/home/adara/raghu_2/dpdk-2.2.0# echo 128 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages

Re: [dpdk-users] Ideal design to use ip-fragmentation using multiple lcores

2018-10-31 Thread Sungho Hong
Thank you very much for the reply, this cleared things up. So in that case, I need a single frag-table correct? so If I want to receive using multiple rx-queues, the fragmented data can arrive at different queues, which means I cannot have multiple frag-table. And does this imply that I have to

Re: [dpdk-users] Failed to allocate tx pool

2018-10-31 Thread Raghu Gangi
Hi Cliff, But I want to allocate memory on only NUMA node where my lcore's and DPDK NICs are connected. I think this gives the most optimized performace when everything is connected to the same NUMA node. Thanks, Raghu -Original Message- From: Raghu Gangi Sent: Wednesday, October 31,

Re: [dpdk-users] Failed to allocate tx pool

2018-10-31 Thread Stephen Hemminger
On Wed, 31 Oct 2018 09:33:34 -0700 Raghu Gangi wrote: > Hi Cliff, > > But I want to allocate memory on only NUMA node where my lcore's and DPDK > NICs are connected. > I think this gives the most optimized performace when everything is connected > to the same NUMA node. > > Thanks, > Raghu >

Re: [dpdk-users] Bring DPDK on ConnectX-3

2018-10-31 Thread Rami Rosen
Hi Quan Not all mlx4 devices are supported by DPDK. What does "lspc -n" how on your host ? This can help in order to see if your device is supported by DPDK . Regards, Rami Rosen בתאריך יום ד׳, 31 באוק׳ 2018, 19:19, מאת : > Hi, > > Recently I have worked on running dpdk on our infiniband card

Re: [dpdk-users] Bring DPDK on ConnectX-3

2018-10-31 Thread Olga Shern
HI Quan, Your NIC is configured to use InfiniBand protocol. InfiniBand is not supported with DPDK , we have it in plans but not with ConnectX-3. Try to change it to ETH and check if works. In general we recommend to use ConnectX-3 Pro at least. Please follow instructions from dpdk.org

[dpdk-users] Possibly wrong RX statistics reported by virtio driver (TRex generator)

2018-10-31 Thread Nikos Anastopoulos
Hi list, The TRex traffic generator's folks recommended us to contact you for an issue that might relate to DPDK virtio driver (https://groups.google.com/forum/#!topic/trex-tgn/LxtTV7G43AE). Specifically, our scenario involves running TRex inside a KVM instance with 2 vhost-user ports,