Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Changpeng Liu <changpeng.liu@intel.com>
Cc: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org, cavery@redhat.com,
	stefanha@redhat.com, pawelx.wodkowski@intel.com,
	james.r.harris@intel.com
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v3] virtio-blk: add discard and write zeroes features to specification
Date: Mon, 12 Mar 2018 17:28:50 +0100	[thread overview]
Message-ID: <f52ee0f7-9eff-e5a0-70de-ece56d9d9b2d@redhat.com> (raw)
In-Reply-To: <bc8d88a4-3069-188a-99aa-c1c75a6e13b2@redhat.com>

On 12/03/2018 17:19, Laszlo Ersek wrote:
> virtio-scsi already supports discard and write zeroes, and virtio-scsi
> can be backed by SSDs. Can you please describe the use case in the
> commit message (in a few words) that needs discard / write zeroes but is
> ill-served by virtio-scsi?
> 
> I believe the spec (and implementations) should be conservative about
> feature duplication unless there's a good reason for it. I don't doubt
> you have a good reason; can you please name it in the commit message?
> I'm not questioning your motives, I'd just like to see them documented
> in the commit log.

Hi Laszlo, the basic reason is that virtio-scsi is slower than
virtio-blk. :)

Indeed DISCARD/WRITE ZEROES was a reason to use virtio-scsi instead of
virtio-blk back when it was created, but at the time DISCARD was
considered a thin provisioning feature; that is, the idea was that
guests could cooperate with the host to save host disk space and to
speed up maintenance operation such as live disk migration.

Nowadays, DISCARD has evolved into a basic disk maintenance operation
and IMO it fits within the scope of virtio-blk, as the backend of choice
for high performance I/O devices.  (Though I wouldn't be surprised
however if, in a few years, virtio-blk has become obsolete and we'll
just use NVMe.  Recent versions of the NVMe spec have taken some
inspiration from Xen and virtio ring buffers, and perform great as
virtual devices; this is a similar "convergence" to what's happening in
virtio for the new packed ring format, just in the opposite direction).

Paolo

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


      parent reply	other threads:[~2018-03-12 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06  2:50 [virtio-dev] [PATCH v3] virtio-blk: add discard and write zeroes features to specification Changpeng Liu
2018-03-07 11:28 ` Stefan Hajnoczi
2018-03-08  1:01   ` Liu, Changpeng
2018-03-08 13:04     ` Paolo Bonzini
2018-03-09  2:31       ` Liu, Changpeng
     [not found] ` <bc8d88a4-3069-188a-99aa-c1c75a6e13b2@redhat.com>
2018-03-12 16:28   ` Paolo Bonzini [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=f52ee0f7-9eff-e5a0-70de-ece56d9d9b2d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=cavery@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=james.r.harris@intel.com \
    --cc=lersek@redhat.com \
    --cc=pawelx.wodkowski@intel.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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