From: Anthony Liguori <aliguori@us.ibm.com>
To: Alex Williamson <alex.williamson@hp.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH] qemu:virtio: Allow guest to defer VIRTIO_F_NOTIFY_ON_EMPTY
Date: Fri, 20 Mar 2009 12:31:29 -0500 [thread overview]
Message-ID: <49C3D2F1.2050305@us.ibm.com> (raw)
In-Reply-To: <20090319162118.24068.98794.stgit@kvm.aw>
Alex Williamson wrote:
> There may be cases where the guest does not want the avail queue
> interrupt, even when it's empty. For the virtio-net case, the
> guest may use a different buffering scheme or decide polling for
> used buffers is more efficient. This can be accomplished by simply
> checking for whether the guest has acknowledged the existing notify
> on empty flag.
>
> Signed-off-by: Alex Williamson <alex.williamson@hp.com>
>
Applied to trunk and stable. Thanks.
Regards,
Anthony Liguori
>
prev parent reply other threads:[~2009-03-20 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 16:21 [Qemu-devel] [PATCH] qemu:virtio: Allow guest to defer VIRTIO_F_NOTIFY_ON_EMPTY Alex Williamson
2009-03-20 17:31 ` Anthony Liguori [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=49C3D2F1.2050305@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=alex.williamson@hp.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).