DPDK usage discussions
 help / color / mirror / Atom feed
From: "Nikos Anastopoulos" <nanastop@intracom-telecom.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Possibly wrong RX statistics reported by virtio driver (TRex generator)
Date: Wed, 31 Oct 2018 10:29:38 +0200	[thread overview]
Message-ID: <814f576a9d9cb240a1cddea3e2b913f9@iris> (raw)

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, 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 transmitted (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 the 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 volume corresponded constantly to 4B-per-packet, for all cases.



The TRex engineers suggested that it seems like an RX counters issues in virtio 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





             reply	other threads:[~2018-10-31  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31  8:29 Nikos Anastopoulos [this message]
2018-10-31 15:25 ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=814f576a9d9cb240a1cddea3e2b913f9@iris \
    --to=nanastop@intracom-telecom.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).