From: Alex Bligh <alex@alex.org.uk>
To: "Denis V. Lunev" <den@openvz.org>
Cc: "nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [RFC 1/1] nbd (specification): add NBD_CMD_WRITE_ZEROES command
Date: Thu, 18 Feb 2016 08:09:48 +0000 [thread overview]
Message-ID: <00466EEA-174D-40E5-B74F-974D11DBB97C@alex.org.uk> (raw)
In-Reply-To: <1455732653-3106-1-git-send-email-den@openvz.org>
On 17 Feb 2016, at 18:10, Denis V. Lunev <den@openvz.org> wrote:
> Currently available NBD_CMD_TRIM command can not be used as the
> specification explicitely says that "a client MUST NOT make any
> assumptions about the contents of the export affected by this
> [NBD_CMD_TRIM] command, until overwriting it again with `NBD_CMD_WRITE`"
Would a flag to NBD_CMD_TRIM that says "ensure the written
data is zeroed" not be an easier solution than adding another
very similar command?
Or (cough) changing the spec?
--
Alex Bligh
next prev parent reply other threads:[~2016-02-18 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 18:10 [Qemu-devel] [RFC 1/1] nbd (specification): add NBD_CMD_WRITE_ZEROES command Denis V. Lunev
2016-02-17 20:58 ` Eric Blake
2016-02-18 4:46 ` Denis V. Lunev
2016-02-18 8:30 ` Denis V. Lunev
2016-02-18 9:18 ` Roman Kagan
2016-02-18 10:36 ` Denis V. Lunev
2016-02-18 16:35 ` Eric Blake
2016-02-18 17:23 ` [Qemu-devel] SUMMARY: " Denis V. Lunev
2016-02-18 17:55 ` Eric Blake
2016-02-18 19:29 ` [Qemu-devel] [Nbd] " Alex Bligh
2016-02-19 7:12 ` [Qemu-devel] " Denis V. Lunev
2016-02-19 8:56 ` Vladimir Sementsov-Ogievskiy
2016-02-19 9:11 ` Daniel P. Berrange
2016-02-18 12:14 ` [Qemu-devel] " Daniel P. Berrange
2016-02-18 14:05 ` Denis V. Lunev
2016-02-18 8:09 ` Alex Bligh [this message]
2016-02-18 8:34 ` Denis V. Lunev
2016-03-04 8:49 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-03-04 9:54 ` Kevin Wolf
2016-03-04 14:03 ` Paolo Bonzini
2016-03-06 10:28 ` Wouter Verhelst
2016-03-06 18:54 ` Denis V. Lunev
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=00466EEA-174D-40E5-B74F-974D11DBB97C@alex.org.uk \
--to=alex@alex.org.uk \
--cc=den@openvz.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=qemu-devel@nongnu.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 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.