From: Jan Kiszka <jan.kiszka@siemens.com>
To: Luke Gorrie <luke@snabb.co>
Cc: Andrew Jones <drjones@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rik van Riel <riel@redhat.com>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [virtio-dev] Zerocopy VM-to-VM networking using virtio-net
Date: Mon, 27 Apr 2015 16:38:47 +0200 [thread overview]
Message-ID: <553E49F7.6010805@siemens.com> (raw)
In-Reply-To: <CAA2XHbd9DX6FXg3Ck++gxHxgr4qLR9ArDQrr+Z5eS7jT+8u-2g@mail.gmail.com>
Am 2015-04-27 um 16:36 schrieb Luke Gorrie:
> On 27 April 2015 at 16:30, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
>> Today, we have posted interrupts to avoid the vm-exit on the target CPU,
>> but there is nothing yet (to my best knowledge) to avoid the exit on the
>> sender side (unless we ignore security). That's the same problem with
>> intra-guest IPIs, BTW.
>>
>> For throughput and given NAPI patterns, that's probably not an issue as
>> you noted. It may be for latency, though, when almost every cycle counts.
>>
>
> Poll-mode networking applications (DPDK, Snabb Switch, etc) are typically
> busy-looping to poll the vring. They may have a very short usleep() between
> checks to save power but they don't wait on their eventfd. So for those
> particular applications latency is on the order of tens of microseconds
> even without guest exits.
That's one side, don't forget the others (the "normal" guests).
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-04-27 14:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150422170138.GA8388@stefanha-thinkpad.redhat.com>
2015-04-22 17:46 ` Zerocopy VM-to-VM networking using virtio-net Cornelia Huck
[not found] ` <20150422194603.1e650ec7.cornelia.huck@de.ibm.com>
2015-04-22 18:00 ` Stefan Hajnoczi
2015-04-23 16:54 ` Cornelia Huck
2015-04-24 8:12 ` [virtio-dev] " Luke Gorrie
2015-04-24 8:20 ` Paolo Bonzini
2015-04-24 9:47 ` Stefan Hajnoczi
2015-04-24 9:50 ` Stefan Hajnoczi
2015-04-24 12:17 ` Luke Gorrie
2015-04-24 13:10 ` Luke Gorrie
2015-04-24 13:23 ` Stefan Hajnoczi
2015-04-24 13:22 ` Stefan Hajnoczi
2015-04-26 13:24 ` Luke Gorrie
2015-04-27 10:17 ` Stefan Hajnoczi
2015-04-27 10:36 ` Michael S. Tsirkin
2015-04-27 12:35 ` Jan Kiszka
2015-04-27 12:55 ` Jan Kiszka
2015-04-27 13:01 ` Stefan Hajnoczi
2015-04-27 13:08 ` Muli Ben-Yehuda
2015-04-27 14:30 ` Jan Kiszka
2015-04-27 14:36 ` Luke Gorrie
2015-04-27 14:38 ` Jan Kiszka [this message]
2015-04-27 14:40 ` Michael S. Tsirkin
2015-04-27 12:57 ` Stefan Hajnoczi
2015-04-27 13:17 ` Michael S. Tsirkin
2015-04-24 12:34 ` Luke Gorrie
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=553E49F7.6010805@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=luke@snabb.co \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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