From: "Liu, Changpeng" <changpeng.liu@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Harris, James R" <james.r.harris@intel.com>,
"Busch, Keith" <keith.busch@intel.com>,
"famz@redhat.com" <famz@redhat.com>,
"stefanha@gmail.com" <stefanha@gmail.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"hch@infradead.org" <hch@infradead.org>,
Daniel Verkamp <dverkamp@chromium.org>
Subject: Re: [Qemu-devel] [RFC v1] block/NVMe: introduce a new vhost NVMe host device to QEMU
Date: Wed, 24 Oct 2018 08:23:40 +0000 [thread overview]
Message-ID: <FF7FC980937D6342B9D289F5F3C7C2625B768443@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20181023193613-mutt-send-email-mst@kernel.org>
The latest thread for supporting DISCARD and WRITE ZEROES feature for virtio-blk is here:
virtio_blk: add discard and write zeroes support
https://lists.linuxfoundation.org/pipermail/virtualization/2018-October/039534.html
I don't take further more steps about it, please go ahead and make the specification more clear, thanks.
> -----Original Message-----
> From: Michael S. Tsirkin [mailto:mst@redhat.com]
> Sent: Wednesday, October 24, 2018 1:39 AM
> To: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Liu, Changpeng <changpeng.liu@intel.com>; qemu-devel@nongnu.org; Harris,
> James R <james.r.harris@intel.com>; Busch, Keith <keith.busch@intel.com>;
> famz@redhat.com; stefanha@gmail.com; stefanha@redhat.com
> Subject: Re: [RFC v1] block/NVMe: introduce a new vhost NVMe host device to
> QEMU
>
> On Tue, Jan 16, 2018 at 06:06:56PM +0100, Paolo Bonzini wrote:
> > Second, virtio-based vhost-user remains QEMU's preferred method for
> > high-performance I/O in guests. Discard support is missing and that is
> > important for SSDs; that should be fixed in the virtio spec.
>
> BTW could you reply on the thread of the patch
> virtio_blk: add discard and write zeroes support
>
> Christoph Hellwig thinks we should change the spec and defer
> implementation until we do. What's your take on this?
>
>
> --
> MST
next prev parent reply other threads:[~2018-10-24 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 8:01 [Qemu-devel] [RFC v1] Introduce a new NVMe host device type to QEMU Changpeng Liu
2018-01-15 8:01 ` [Qemu-devel] [RFC v1] block/NVMe: introduce a new vhost NVMe host device " Changpeng Liu
2018-01-16 17:06 ` Paolo Bonzini
2018-01-17 0:53 ` Liu, Changpeng
2018-01-17 7:10 ` Paolo Bonzini
2018-10-23 23:39 ` Michael S. Tsirkin
2018-10-24 8:23 ` Liu, Changpeng [this message]
2018-01-29 15:29 ` Stefan Hajnoczi
2018-01-29 15:40 ` Harris, James R
2018-01-30 1:19 ` Liu, Changpeng
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=FF7FC980937D6342B9D289F5F3C7C2625B768443@SHSMSX103.ccr.corp.intel.com \
--to=changpeng.liu@intel.com \
--cc=dverkamp@chromium.org \
--cc=famz@redhat.com \
--cc=hch@infradead.org \
--cc=james.r.harris@intel.com \
--cc=keith.busch@intel.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 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.