From: Stefan Baranoff <sbaranoff@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] XL710 KVM SR-IOV 4ms/8ms Latency
Date: Tue, 13 Mar 2018 12:16:00 -0400 [thread overview]
Message-ID: <CAHzKxpYgAOXW6jDjj7HBPUSM4kevPJJx=CFFi1Y_6VtXaxJVDg@mail.gmail.com> (raw)
All,
We're seeing an odd 8ms latency under low load through a virtualized DPDK
application. Even a very simple, basic, l2fwd style application exhibits
this behavior. Our environment is:
Host:
CentOS 7.4 - fully updated
2 x Intel Gold 6148 CPU
384 GB of RAM in 12 x 32GB configuration
Intel XL710 NIC configured for SR-IOV using host PF (driver is CentOS
default version)
Guest:
KVM (libvirt) based - cpu mode = host-model, features = acpi, apic, pae
CentOS 7.4 - full updated
8 logic cores
32 GB of RAM
2 DPDK NICs are SR-IOV XL710 VFs passed through
Running a single ICMP echo request/response (ping) through an l2fwd
equivalent on the VM results in mostly 8ms RTTs with a few sub-1ms RTTs.
Switching to a Linux bridge we see sub-1ms latencies.
Using the physical function on the physical host with the same application
we do not see such latency.
Any ideas?
Thanks,
Stefan
reply other threads:[~2018-03-13 16:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHzKxpYgAOXW6jDjj7HBPUSM4kevPJJx=CFFi1Y_6VtXaxJVDg@mail.gmail.com' \
--to=sbaranoff@gmail.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).