From: Mark McLoughlin <markmc@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Davide Libenzi <davidel@xmailserver.org>,
mtosatti@redhat.com
Subject: Re: [KVM PATCH v4 3/3] kvm: add iosignalfd support
Date: Wed, 27 May 2009 17:25:44 +0000 [thread overview]
Message-ID: <1243445144.16318.15.camel@blaa> (raw)
In-Reply-To: <4A1D2DD8.2050709@redhat.com>
On Wed, 2009-05-27 at 15:11 +0300, Avi Kivity wrote:
> Multiple cookies on the same address are required by virtio. You can't
> mux since the data doesn't go anywhere.
>
> Virtio can survive by checking all rings on a notify, and we can later
> add a mechanism that has a distinct address for each ring, but let's see
> if we can cope with multiple cookies. Mark?
Trying to catch up, but you're talking about replacing virtio-pci
QUEUE_NOTIFY handling with iosignalfd ?
For a perfect replacement, what you really need is to be able to
register multiple cookies per address range, but only have them trigger
if the written data matches a provided value.
If the data is lost, virtio has no way of knowing which queue is being
notified, so we either end up with per-device, rather than per-queue,
notifications (probably not too bad for net, at least) or a different
notify address per queue (limiting the number of queues per device).
Cheers,
Mark.
next prev parent reply other threads:[~2009-05-27 17:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 19:15 [KVM PATCH v4 0/3] iosignalfd Gregory Haskins
2009-05-26 19:15 ` [KVM PATCH v4 1/3] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-27 8:57 ` Avi Kivity
2009-05-27 11:53 ` Gregory Haskins
2009-05-26 19:15 ` [KVM PATCH v4 2/3] kvm: make io_bus interface more robust Gregory Haskins
2009-05-27 8:54 ` Avi Kivity
2009-05-27 11:26 ` Gregory Haskins
2009-05-26 19:15 ` [KVM PATCH v4 3/3] kvm: add iosignalfd support Gregory Haskins
2009-05-27 9:03 ` Avi Kivity
2009-05-27 11:47 ` Gregory Haskins
2009-05-27 12:11 ` Avi Kivity
2009-05-27 12:54 ` Gregory Haskins
2009-05-27 17:25 ` Mark McLoughlin [this message]
2009-05-27 17:40 ` Gregory Haskins
2009-05-27 17:48 ` Mark McLoughlin
2009-05-27 20:45 ` Gregory Haskins
2009-05-28 9:09 ` Mark McLoughlin
2009-05-28 12:12 ` Gregory Haskins
2009-05-31 9:11 ` Avi Kivity
2009-06-01 12:14 ` Gregory Haskins
2009-06-03 22:04 ` Gregory Haskins
2009-06-04 13:20 ` Mark McLoughlin
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=1243445144.16318.15.camel@blaa \
--to=markmc@redhat.com \
--cc=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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.