From: Fam Zheng <famz@redhat.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Kevin Wolf <kwolf@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Max Reitz <mreitz@redhat.com>,
"borntraeger@de.ibm.com" <borntraeger@de.ibm.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Karl Rister <krister@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] RFC: A VFIO based block driver for NVMe device
Date: Fri, 30 Dec 2016 08:46:51 +0800 [thread overview]
Message-ID: <20161230004651.GA24498@lemon> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D190BEED9B@SHSMSX101.ccr.corp.intel.com>
On Thu, 12/29 04:09, Tian, Kevin wrote:
> is it a tradeoff between performance (better than linux-aio) and composability
> (snapshot and live migration which not supported by direct passthrough)?
Yes.
Fam
prev parent reply other threads:[~2016-12-30 0:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 16:31 [Qemu-devel] [PATCH 0/4] RFC: A VFIO based block driver for NVMe device Fam Zheng
2016-12-20 16:31 ` [Qemu-devel] [PATCH 1/4] ramblock-notifier: new Fam Zheng
2016-12-22 9:56 ` Paolo Bonzini
2017-01-11 5:38 ` Stefan Weil
2017-01-11 5:48 ` Stefan Weil
2017-01-11 6:41 ` Fam Zheng
2016-12-20 16:31 ` [Qemu-devel] [PATCH 2/4] util: Add a notifier list for qemu_vfree() Fam Zheng
2016-12-20 16:31 ` [Qemu-devel] [PATCH 3/4] util: Add VFIO helper library Fam Zheng
2016-12-21 15:46 ` Paolo Bonzini
2016-12-21 16:19 ` Fam Zheng
2016-12-21 17:02 ` Paolo Bonzini
2016-12-20 16:31 ` [Qemu-devel] [PATCH 4/4] block: Add VFIO based NVMe driver Fam Zheng
2016-12-20 16:39 ` Paolo Bonzini
2016-12-21 11:59 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-12-21 14:05 ` Fam Zheng
2016-12-20 23:04 ` [Qemu-devel] [PATCH 0/4] RFC: A VFIO based block driver for NVMe device no-reply
2016-12-21 1:38 ` Fam Zheng
2016-12-21 0:48 ` no-reply
2016-12-29 4:09 ` Tian, Kevin
2016-12-30 0:46 ` Fam Zheng [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=20161230004651.GA24498@lemon \
--to=famz@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=kevin.tian@intel.com \
--cc=krister@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).