From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
dlaor@redhat.com, virtualization@lists.linux-foundation.org,
Chris Wright <chrisw@redhat.com>,
Mark McLoughlin <markmc@redhat.com>,
kvm@vger.kernel.org, Brian Stein <bstein@redhat.com>,
Herbert Xu <herbert.xu@redhat.com>, Dor Laor <dor@redhat.com>,
Yaron Haviv <yaronh@voltaire.com>,
Shahar Klein <shahark@voltaire.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: TODO list for qemu+KVM networking performance v2
Date: Wed, 10 Jun 2009 18:18:01 +0300 [thread overview]
Message-ID: <4A2FCEA9.8010604@redhat.com> (raw)
In-Reply-To: <20090610145358.GB28601@redhat.com>
Michael S. Tsirkin wrote:
> But I don't understand how aio will make implementing it easier -
> or are you merely saying that it will make it worthwhile?
>
If you have aio, the the NIC and the guest proceed in parallel. If the
guest is faster (likely), then when it sends the next packet it will see
that interrupts are disabled and not notify again. Once aio complete we
can recheck the queue; if it's empty we reenable notifications. If
there's still stuff in it we submit it with notifications disabled.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-10 15:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 16:43 TODO list for qemu+KVM networking performance v2 Michael S. Tsirkin
2009-06-04 17:16 ` Gregory Haskins
2009-06-04 17:16 ` Gregory Haskins
2009-06-04 17:29 ` Michael S. Tsirkin
2009-06-04 17:29 ` Michael S. Tsirkin
2009-06-04 17:50 ` Gregory Haskins
2009-06-04 18:10 ` Michael S. Tsirkin
2009-06-04 18:10 ` Michael S. Tsirkin
2009-06-04 17:50 ` Gregory Haskins
2009-06-10 3:39 ` Rusty Russell
2009-06-10 3:39 ` Rusty Russell
2009-06-10 6:26 ` Dor Laor
2009-06-10 6:26 ` Dor Laor
2009-06-10 14:39 ` Rusty Russell
2009-06-10 14:53 ` Michael S. Tsirkin
2009-06-10 14:53 ` Michael S. Tsirkin
2009-06-10 15:18 ` Avi Kivity [this message]
2009-06-10 15:54 ` Michael S. Tsirkin
2009-06-10 16:08 ` Avi Kivity
2009-06-10 16:28 ` Michael S. Tsirkin
2009-06-10 16:28 ` Michael S. Tsirkin
2009-06-10 16:08 ` Avi Kivity
2009-06-10 15:54 ` Michael S. Tsirkin
2009-06-10 15:18 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-06-04 16:43 Michael S. Tsirkin
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=4A2FCEA9.8010604@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=bstein@redhat.com \
--cc=chrisw@redhat.com \
--cc=dlaor@redhat.com \
--cc=dor@redhat.com \
--cc=herbert.xu@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=shahark@voltaire.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yaronh@voltaire.com \
/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.