From: Scott Sullivan <ssullivan@liquidweb.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] is x-data-plane considered "stable" ?
Date: Thu, 02 Oct 2014 11:20:55 -0400 [thread overview]
Message-ID: <542D6D57.7060702@liquidweb.com> (raw)
Can anyone tell me if in any QEMU release x-data-plane is considered "stable"?
If its unclear, I am referring to the feature introduced in QEMU 1.4 for high performance disk I/O called virtio-blk data plane.
http://blog.vmsplice.net/2013/03/new-in-qemu-14-high-performance-virtio.html
I've tried searching docs, but can't find any mention if its still considered experimental or not in the latest QEMU releases.
next reply other threads:[~2014-10-02 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 15:20 Scott Sullivan [this message]
2014-10-03 10:11 ` [Qemu-devel] is x-data-plane considered "stable" ? Alexandre DERUMIER
2014-10-03 13:40 ` Paolo Bonzini
2014-10-03 13:47 ` Scott Sullivan
2014-10-03 14:26 ` Alexandre DERUMIER
2014-10-03 15:33 ` Paolo Bonzini
2014-10-03 15:34 ` Alexandre DERUMIER
2014-10-04 18:21 ` Stefan Hajnoczi
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=542D6D57.7060702@liquidweb.com \
--to=ssullivan@liquidweb.com \
--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).