From: Julian Stecklina <jsteckli@os.inf.tu-dresden.de>
To: David Mohr <damailings@mcbf.net>
Cc: <kvm@vger.kernel.org>
Subject: Re: Networking latency - what to expect?
Date: Thu, 29 Nov 2012 17:35:51 +0100 [thread overview]
Message-ID: <87hao8jriw.fsf@os.inf.tu-dresden.de> (raw)
In-Reply-To: <f9112ea5aed92fe8fb381122acfb880c@de.mcbf.net> (David Mohr's message of "Thu, 29 Nov 2012 08:50:41 -0700")
Thus spake David Mohr <damailings@mcbf.net>:
> On 2012-11-29 07:48, Julian Stecklina wrote:
>> Thus spake David Mohr <damailings@mcbf.net>:
>>
>>> * vm->vm (same host) 22k
>>
>> This number is in the same ballpark as what I am seeing on pretty
>> much
>> the same hardware.
>>
>> AFAICS, there is little you can do to the current virtio->virtio code
>> path that would make this substantially faster.
>
> Thanks for the feedback. Considering that it's better than the
> hardware network performance my main issue is actually the latency of
> communication between VMs on different hosts:
> * vm->vm (diff. hosts) 7k
>
> It is obvious that there is a lot more going on compared to same host
> communication, but only ~30% of the performance when the network
> hardware should not be slowing it down (too) much?
You are probably better of using SR-IOV NICs with PCI passthrough in
this case.
Maybe someone can comment on whether virtual interrupt delivery and
posted interrupts[1] are already usable. The first one should help in
either the virtio and SR-IOV scenarios, the latter only applies to
SR-IOV (and PCI passthrough in general).
Julian
[1] http://www.spinics.net/lists/kvm/msg82762.html
prev parent reply other threads:[~2012-11-29 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 23:26 Networking latency - what to expect? David Mohr
2012-11-29 14:48 ` Julian Stecklina
2012-11-29 15:50 ` David Mohr
2012-11-29 16:35 ` Julian Stecklina [this message]
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=87hao8jriw.fsf@os.inf.tu-dresden.de \
--to=jsteckli@os.inf.tu-dresden.de \
--cc=damailings@mcbf.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox