From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from extvmail.intracom-telecom.com (extvmail.intracom-telecom.com [192.92.155.2]) by dpdk.org (Postfix) with ESMTP id BCCC52BAB for ; Wed, 31 Oct 2018 09:29:43 +0100 (CET) Received: from mailserv.intracomtel.com (mailserv [146.124.14.106]) by extvmail.intracom-telecom.com (8.14.7/8.14.7) with ESMTP id w9V8TgHM101413 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 31 Oct 2018 10:29:42 +0200 Received: from mailserv.intracomtel.com (localhost [127.0.0.1]) by mailserv.intracomtel.com (8.14.7/8.14.7) with ESMTP id w9V8ThSP012089 for ; Wed, 31 Oct 2018 10:29:43 +0200 Received: from iris.intracomtel.com (iris.intracomtel.com [10.127.1.100]) by mailserv.intracomtel.com (8.14.7/8.14.7) with ESMTP id w9V8Tg6f012085 for ; Wed, 31 Oct 2018 10:29:42 +0200 Received: from [10.124.83.78] (account nanastop@iris.intracomtel.com) by iris.intracomtel.com (CommuniGate Pro IMAP 6.1.18) with XMIT id 106951168 for users@dpdk.org; Wed, 31 Oct 2018 10:29:42 +0200 Date: Wed, 31 Oct 2018 10:29:38 +0200 Message-Id: <814f576a9d9cb240a1cddea3e2b913f9@iris> MIME-Version: 1.0 Thread-Topic: Possibly wrong RX statistics reported by virtio driver (TRex generator) Priority: Normal Importance: normal X-MSMail-Priority: normal X-Priority: 3 Sensitivity: Normal Thread-Index: AdRw8zYeUgWE6O1cT+W1nsQEmLuTRA== From: "Nikos Anastopoulos" To: "users@dpdk.org" X-Mailer: CommuniGate Pro MAPI Connector 1.52.54.11/1.54.12.20 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSS-9.1.0.1213-8.2.0.1013-24190.005 X-TMASE-Version: IMSS-9.1.0.1213-8.2.1013-24190.005 X-TMASE-Result: 10--15.136100-10.000000 X-TMASE-MatchedRID: OKw9jwRws6lUJiuzzlItyhMxKDqgAFSzBdebOqawiLsKr8NTiM/VplPW us3yxQNW/nk73pB6+J+KTvaW2OiqPc6RSKW8ae597spMO3HwKCC+JGWINXafLPBnFoUlf6vVrKp xJFOha4w6BYHg0vdHoJacL8eCHb878EOSfpJbOopgP1dNF1ow7UqAhuLHn5fEJtZH9tzUWm5/9t MKhlGm0jba6gSbbjl+WBQVNPtj1ClhNnaZf6fHDBuurbgYp+HQ6r+5bPPauHf5N0o2THGRZKgFX 2xz5NjH4j4lr4Wn4RisEFKef8ZUxqf50/sZyNUdb/5HBZ6dvRh3Bf9JIqsoeEbaqUVvLFsixNxv PmI6N152+AZuxakJy1x59CtgmyHsxGjrj8wW9k0ZS5uxXPxN6dVYleRFiu07myiLZetSf8mVHVx P1hp9BR8AKgKWeNGhA2cEfhFp/Ys7AFczfjr/7EmFcuL0kr8c+S+e4Ov3uyahUkRv8AGZlWwo3J 9ZBQaoqZ52QhQYxUs= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Possibly wrong RX statistics reported by virtio driver (TRex generator) 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: Wed, 31 Oct 2018 08:29:44 -0000 Hi list, The TRex traffic generator's folks recommended us to contact you for an iss= ue 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, which are connected in loopback mode via an OVS-DPDK (= i.e. whatever sent through port1 goes to port2, and vice versa). We observe= that the received traffic volume reported by TRex is much less than the tr= ansmitted (it is constantly 4B per packet), whereas: 1) the count of the received packets is the same 2) the contents of the received packets, as captured _inside_ the VM, are t= he same with the transmitted Specifically, we experimented with different packet sizes being transmitted= , i.e. 64B, 150B, 1000B, yet in the receive path the reported incoming volu= me corresponded constantly to 4B-per-packet, for all cases. The TRex engineers suggested that it seems like an RX counters issues in vi= rtio driver. Experimental setup: - TRex v2.45 (uses DPDK 17.11 AFAIK), within a QEMU v2.12 - on the host: OVS 2.10.0 with DPDK 17.11.3 Thanks, Nikos