From: Eric Tremblay <ertr@kaloom.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Virtio-user exceptional path performance
Date: Tue, 4 Sep 2018 17:54:20 +0000 [thread overview]
Message-ID: <YQBPR0101MB1538C2074DB82D898A6A42B2AF030@YQBPR0101MB1538.CANPRD01.PROD.OUTLOOK.COM> (raw)
Hello,
I am testing the performance capabilities of the virtio-user exceptional path for use in container networking scenarios. I am trying to reproduce the results obtained in Test Case 1 described in the paper "VIRTIO-USER: A New Versatile Channel for Kernel-Bypass Networks". That is, I am creating two virtio-user vdevs in testpmd, putting each one in separate network namespaces and running iperf3 between the two. However, I am unable to obtain the near 25Gbps throughput shown in the paper. Instead, I obtained a mere 3Gbps. Has anyone else been able to reproduce these results? My understanding is that this type of virtual device takes advantage of both checksum offloading and LRO in order to get such high throughput. However, for some reason, I am unable to use RX checksum offloading nor LRO in my setup. If I specify the --enable-lro and --enable-rx-cksum options in testpmd (as shown here https://doc.dpdk.org/guides-17.11/howto/virtio_user_as_exceptional_path.html), the tap device is never created in the kernel. If I do not specify these options, the tap is created correctly but the rx-checksum and LRO are off and cannot be turned on using ethtool (they are marked as [fixed]).
Does anyone have any idea what may be preventing me from taking advantage of checksum offloading and LRO? Also, I am I right in assuming that this is the reason why the performance is so poor or could there be another problem with my setup? I am using DPDK 17.11 on CentOS 7.5. Any help would be appreciated.
Regards,
Eric
next reply other threads:[~2018-09-04 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 17:54 Eric Tremblay [this message]
2018-09-18 5:29 ` Tiwei Bie
2018-09-18 14:45 ` Eric Tremblay
2018-09-19 5:08 ` Tiwei Bie
2018-09-24 15:25 ` Eric Tremblay
2018-10-08 4:48 ` Tiwei Bie
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=YQBPR0101MB1538C2074DB82D898A6A42B2AF030@YQBPR0101MB1538.CANPRD01.PROD.OUTLOOK.COM \
--to=ertr@kaloom.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).