From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Changpeng" <changpeng.liu@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "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>,
"mst@redhat.com" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC v1] block/NVMe: introduce a new vhost NVMe host device to QEMU
Date: Wed, 17 Jan 2018 08:10:50 +0100 [thread overview]
Message-ID: <fa671cfd-f03d-5f12-9797-f1c7d9e7583c@redhat.com> (raw)
In-Reply-To: <FF7FC980937D6342B9D289F5F3C7C2625B5EFE58@SHSMSX103.ccr.corp.intel.com>
On 17/01/2018 01:53, Liu, Changpeng 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. Are there
> Previously I have a patch adding DISCARD support to virtio-blk, but I didn't find
> the way using svn to update the spec patch, any git repository I can use
> to update the virtio-blk spec ? I think I can pick up the feature again.
There is https://github.com/oasis-tcs/virtio-spec.
You should add support for all of:
1) a command that can do WRITE ZERO, WRITE ZERO with discard, and
advisory DISCARD of a range of blocks. The command must be controlled
by a new feature bit.
2) a configuration space element for discard granularity, controlled by
the same feature bit as (1)
3) a feature bit that is 1 if WRITE ZERO with discard can actually
discard parts that are aligned to the granularity
Thanks,
Paolo
next prev parent reply other threads:[~2018-01-17 7:11 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 [this message]
2018-10-23 23:39 ` Michael S. Tsirkin
2018-10-24 8:23 ` Liu, Changpeng
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=fa671cfd-f03d-5f12-9797-f1c7d9e7583c@redhat.com \
--to=pbonzini@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=famz@redhat.com \
--cc=james.r.harris@intel.com \
--cc=keith.busch@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).