Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: virtio-dev@lists.oasis-open.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: [virtio-dev] [PATCH v2 3/4] virtio-blk: describe write zeroes unmap semantics
Date: Thu, 31 Jan 2019 10:36:16 +0800	[thread overview]
Message-ID: <20190131023617.23007-4-stefanha@redhat.com> (raw)
In-Reply-To: <20190131023617.23007-1-stefanha@redhat.com>

Explain the meaning of the unmap flag.  The details are already covered
in the device normative section but mentioning it here makes the text
easier to understand.

Suggested-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 content.tex | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content.tex b/content.tex
index 4201c7e..8ea8320 100644
--- a/content.tex
+++ b/content.tex
@@ -3983,7 +3983,9 @@ struct virtio_blk_discard_write_zeroes {
 
 \field{sector} indicates the starting offset (in 512-byte units) of the
 segment, while \field{num_sectors} indicates the number of sectors in each
-discarded range. \field{unmap} is only used for write zeroes command.
+discarded range. \field{unmap} is only used in write zeroes commands and allows
+the device to discard the specified range, provided that following reads return
+zeroes.
 
 The final \field{status} byte is written by the device: either
 VIRTIO_BLK_S_OK for success, VIRTIO_BLK_S_IOERR for device or driver
-- 
2.20.1


---------------------------------------------------------------------
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:[~2019-01-31  2:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  2:36 [virtio-dev] [PATCH v2 0/4] virtio-blk: discard and write zeroes clarifications Stefan Hajnoczi
2019-01-31  2:36 ` [virtio-dev] [PATCH v2 1/4] virtio-blk: document data[] size constraints Stefan Hajnoczi
2019-01-31  4:14   ` [virtio-dev] " Michael S. Tsirkin
2019-02-18  7:22     ` Jan Kiszka
2019-02-18 14:04       ` Stefan Hajnoczi
2019-02-20  3:49         ` Michael S. Tsirkin
2019-02-22  5:53         ` Michael S. Tsirkin
2019-02-22  9:55           ` Stefan Hajnoczi
2019-01-31  2:36 ` [virtio-dev] [PATCH v2 2/4] virtio-blk: move virtio_blk_discard_write_zeroes definition Stefan Hajnoczi
2019-01-31  2:36 ` Stefan Hajnoczi [this message]
2019-01-31  2:36 ` [virtio-dev] [PATCH v2 4/4] virtio-blk: avoid inconsistent "DISCARD" term 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=20190131023617.23007-4-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=mst@redhat.com \
    --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