From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out11.electric.net (smtp-out11.electric.net [185.38.181.38]) by dpdk.org (Postfix) with ESMTP id 49D0C5A8D for ; Tue, 2 May 2017 14:20:59 +0200 (CEST) Received: from 1d5Wnb-0006ZH-UT by out11d.electric.net with emc1-ok (Exim 4.87) (envelope-from ) id 1d5Wnb-0006Za-V3 for users@dpdk.org; Tue, 02 May 2017 05:20:59 -0700 Received: by emcmailer; Tue, 02 May 2017 05:20:59 -0700 Received: from [192.36.1.72] (helo=mx-3.enea.com) by out11d.electric.net with esmtps (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.87) (envelope-from ) id 1d5Wnb-0006ZH-UT for users@dpdk.org; Tue, 02 May 2017 05:20:59 -0700 Received: from SESTOEX04.enea.se ([fe80::bc2d:9299:d6b2:d0b7]) by SESTOEX03.enea.se ([fe80::6ce7:7b51:1edf:e245%17]) with mapi id 14.03.0319.002; Tue, 2 May 2017 14:20:38 +0200 From: Gabriel Ionescu To: "users@dpdk.org" Thread-Topic: Issue with Pktgen and OVS-DPDK Thread-Index: AdLDHc9SyeONySmmS621uQ4vR+H+Dw== Date: Tue, 2 May 2017 12:20:37 +0000 Message-ID: <05AD9C758FB3CB46912B9395C8B3C047015B76FA@SESTOEX04.enea.se> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.15.85] MIME-Version: 1.0 X-Outbound-IP: 192.36.1.72 X-Env-From: Gabriel.Ionescu@enea.com X-Proto: esmtps X-Revdns: mx-3.enea.com X-HELO: mx-3.enea.com X-TLS: TLSv1:ECDHE-RSA-AES256-SHA:256 X-Authenticated_ID: X-PolicySMART: 6551647 X-Virus-Status: Scanned by VirusSMART (c) X-Virus-Status: Scanned by VirusSMART (s) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Issue with Pktgen and OVS-DPDK X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 May 2017 12:21:00 -0000 Hi, I am using DPDK-Pktgen with an OVS bridge that has two vHost-user ports and= I am seeing an issue where Pktgen does not look like it generates packets = correctly. For this setup I am using DPDK 17.02, Pktgen 3.2.8 and OVS 2.7.0. The OVS bridge is created with: ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=3Dnetdev ovs-vsctl add-port ovsbr0 vhost-user1 -- set Interface vhost-user1 type=3Dd= pdkvhostuser ofport_request=3D1 ovs-vsctl add-port ovsbr0 vhost-user2 -- set Interface vhost-user2 type=3Dd= pdkvhostuser ofport_request=3D2 ovs-ofctl add-flow ovsbr0 in_port=3D1,action=3Doutput:2 ovs-ofctl add-flow ovsbr0 in_port=3D2,action=3Doutput:1 DPDK-Pktgen is launched with the following command so that packets generate= d through port 0 are received by port 1 and viceversa: pktgen -c 0xF --file-prefix pktgen --no-pci \ --vdev=3Dvirtio_user0,path=3D/tmp/vhost-use= r1 \ --vdev=3Dvirtio_user1,path=3D/tmp/vhost-use= r2 \ -- -P -m "[0:1].0, [2:3].1" In Pktgen, the default settings are used for both ports: - Tx Count: Forever - Rate: 100% - PktSize: 64 - Tx Burst: 32 Whenever I start generating packets through one of the ports (in this examp= le port 0 by running start 0), the OVS logs throw warnings similar to: 2017-05-02T09:23:04.741Z|00022|netdev_dpdk(pmd9)|WARN|Dropped 1194956 log m= essages in last 49 seconds (most recently, 41 seconds ago) due to excessive= rate 2017-05-02T09:23:04.741Z|00023|netdev_dpdk(pmd9)|WARN|vhost-user2: Too big = size 1524 max_packet_len 1518 2017-05-02T09:23:04.741Z|00024|netdev_dpdk(pmd9)|WARN|vhost-user2: Too big = size 1524 max_packet_len 1518 2017-05-02T09:23:04.741Z|00025|netdev_dpdk(pmd9)|WARN|vhost-user2: Too big = size 1524 max_packet_len 1518 2017-05-02T09:23:04.741Z|00026|netdev_dpdk(pmd9)|WARN|vhost-user2: Too big = size 1524 max_packet_len 1518 2017-05-02T09:23:15.761Z|00027|netdev_dpdk(pmd9)|WARN|Dropped 1344988 log m= essages in last 11 seconds (most recently, 0 seconds ago) due to excessive = rate 2017-05-02T09:23:15.761Z|00028|netdev_dpdk(pmd9)|WARN|vhost-user2: Too big = size 57564 max_packet_len 1518 Port 1 does not receive any packets. When running Pktgen with the -socket-mem option (e.g. --socket-mem 512), th= e behavior is different, but with the same warnings thrown by OVS: port 1 r= eceives some packages, but with different sizes, even though they are gener= ated on port 0 with a 64b size: Flags:Port : P--------------:0 P--------------:1 Link State : ----TotalRa= te---- Pkts/s Max/Rx : 0/0 35136/0 3= 5136/0 Max/Tx : 238144/25504 0/0 238144= /25504 MBits/s Rx/Tx : 0/13270 0/0 0= /13270 Broadcast : 0 0 Multicast : 0 0 64 Bytes : 0 288 65-127 : 0 1440 128-255 : 0 2880 256-511 : 0 6336 512-1023 : 0 12096 1024-1518 : 0 12096 Runts/Jumbos : 0/0 0/0 Errors Rx/Tx : 0/0 0/0 Total Rx Pkts : 0 35136 Tx Pkts : 1571584 0 Rx MBs : 0 227 Tx MBs : 412777 0 ARP/ICMP Pkts : 0/0 0/0 : Pattern Type : abcd... abcd... Tx Count/% Rate : Forever /100% Forever /100% PktSize/Tx Burst : 64 / 32 64 / 32 Src/Dest Port : 1234 / 5678 1234 / 5678 Pkt Type:VLAN ID : IPv4 / TCP:0001 IPv4 / TCP:0001 Dst IP Address : 192.168.1.1 192.168.0.1 Src IP Address : 192.168.0.1/24 192.168.1.1/24 Dst MAC Address : a6:71:4e:2f:ee:5d b6:38:dd:34:b2:93 Src MAC Address : b6:38:dd:34:b2:93 a6:71:4e:2f:ee:5d VendID/PCI Addr : 0000:0000/00:00.0 0000:0000/00:00.0 -- Pktgen Ver: 3.2.8 (DPDK 17.02.0) Powered by Intel(r) DPDK -------------= ------ If packets are generated from an external source and testpmd is used to for= ward traffic between the two vHost-user ports, the warnings are not thrown = by the OVS bridge. Should this setup work? Is this an issue or am I setting something up wrong? Thank you, Gabriel Ionescu