From: Alex Williamson <alex.williamson@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: performance of virtual functions compared to virtio
Date: Mon, 25 Apr 2011 14:27:34 -0600 [thread overview]
Message-ID: <1303763254.3431.79.camel@x201> (raw)
In-Reply-To: <4DB5D053.1070401@gmail.com>
On Mon, 2011-04-25 at 13:49 -0600, David Ahern wrote:
>
> On 04/25/11 13:29, Alex Williamson wrote:
> > So we're effectively getting host-host latency/throughput for the VF,
> > it's just that in the 82576 implementation of SR-IOV, the VF takes a
> > latency hit that puts it pretty close to virtio. Unfortunate. I think
>
> For host-to-VM using VFs is worse than virtio which is counterintuitive.
On the same host, just think about the data path of one versus the
other. On the guest side, there's virtio vs a physical NIC. virtio is
designed to be virtualization friendly, so hopefully has less context
switches in setting up and processing transactions. Once the packet
leaves the assigned physical NIC, it has to come back up the entire host
I/O stack, while the virtio device is connected to an internal bridge
and bypasses all but the upper level network routing.
> > you'll find that passing the PF to the guests should be pretty close to
> > that 185us latency. I would assume (hope) the higher end NICs reduce
>
> About that 185usec: do you know where the bottleneck is? It seems as if
> the packet is held in some queue waiting for an event/timeout before it
> is transmitted.
I don't know specifically, I don't do much network performance tuning.
Interrupt coalescing could be a factor, along with various offload
settings, and of course latency of the physical NIC hardware and
interconnects. Thanks,
Alex
next prev parent reply other threads:[~2011-04-25 20:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 1:57 performance of virtual functions compared to virtio David Ahern
2011-04-21 2:35 ` Alex Williamson
2011-04-21 8:07 ` Avi Kivity
2011-04-21 12:31 ` Stefan Hajnoczi
2011-04-21 13:09 ` Avi Kivity
2011-04-25 17:49 ` David Ahern
2011-04-26 8:19 ` Avi Kivity
2011-04-27 21:13 ` David Ahern
2011-04-28 8:07 ` Avi Kivity
2011-04-25 17:46 ` David Ahern
2011-04-26 8:20 ` Avi Kivity
2011-04-25 17:39 ` David Ahern
2011-04-25 18:13 ` Alex Williamson
2011-04-25 19:07 ` David Ahern
2011-04-25 19:29 ` Alex Williamson
2011-04-25 19:49 ` David Ahern
2011-04-25 20:27 ` Alex Williamson [this message]
2011-04-25 20:40 ` David Ahern
2011-04-25 21:02 ` Alex Williamson
2011-04-25 21:14 ` David Ahern
2011-04-25 21:18 ` Alex Williamson
2011-04-25 20:49 ` Andrew Theurer
2011-05-02 18:58 ` David Ahern
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=1303763254.3431.79.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=dsahern@gmail.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.