From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Wouter Verhelst <w@uter.be>, Eric Blake <eblake@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu-block@nongnu.org, nbd-general@lists.sourceforge.net,
"Denis V. Lunev" <den@openvz.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] write_zeroes/trim on the whole disk
Date: Mon, 26 Sep 2016 10:47:15 +0200 [thread overview]
Message-ID: <20160926084715.GC6093@noname.str.redhat.com> (raw)
In-Reply-To: <57E67120.1040409@virtuozzo.com>
Am 24.09.2016 um 14:27 hat Vladimir Sementsov-Ogievskiy geschrieben:
> On 24.09.2016 15:06, Vladimir Sementsov-Ogievskiy wrote:
> >On 24.09.2016 00:21, Wouter Verhelst wrote:
> >>On Fri, Sep 23, 2016 at 02:00:06PM -0500, Eric Blake wrote:
> >>>My preference would be a new flag to the existing commands, with
> >>>explicit documentation that 0 offset and 0 length must be used
> >>>with that
> >>>flag, when requesting a full-device wipe.
> >>Alternatively, what about a flag that says "if you use this flag, the
> >>size should be left-shifted by X bits before processing"? That allows
> >>you to do TRIM or WRITE_ZEROES on much larger chunks, without being
> >>limited to "whole disk" commands. We should probably make it an illegal
> >>flag for any command that actually sends data over the wire, though.
> >>
> >
> >
> >Note: if disk size is not aligned to X we will have to send
> >request larger than the disk size to clear the whole disk.
> >
>
> Also, in this case, which realization of bdrv interface in qemu
> would be most appropriate? Similar flag (in this case X must be
> defined in some very transparent way, as a constant of 64k for
> example), or flag BDRV_REQ_WHOLE_DISK, or separate .bdrv_zero_all
> and .bdrv_discard_all ?
Maybe the best would be to extend the existing discard/write_zeroes
functions to take a 64 bit byte count and then NBD can internally
check whether a request clears the whole disk.
Kevin
next prev parent reply other threads:[~2016-09-26 8:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 18:32 [Qemu-devel] write_zeroes/trim on the whole disk Vladimir Sementsov-Ogievskiy
2016-09-23 19:00 ` Eric Blake
2016-09-23 21:21 ` Wouter Verhelst
2016-09-24 7:54 ` Denis V. Lunev
2016-09-24 10:31 ` [Qemu-devel] [Nbd] " Alex Bligh
2016-09-24 22:07 ` Wouter Verhelst
2016-09-24 12:06 ` [Qemu-devel] " Vladimir Sementsov-Ogievskiy
2016-09-24 12:27 ` Vladimir Sementsov-Ogievskiy
2016-09-26 8:47 ` Kevin Wolf [this message]
2016-09-26 12:49 ` Paolo Bonzini
2016-09-24 13:42 ` Vladimir Sementsov-Ogievskiy
2016-09-24 16:20 ` Vladimir Sementsov-Ogievskiy
2016-09-24 16:35 ` Alex Bligh
2016-09-24 16:44 ` Vladimir Sementsov-Ogievskiy
2016-09-24 16:48 ` Vladimir Sementsov-Ogievskiy
2016-09-24 16:52 ` Alex Bligh
2016-09-24 17:01 ` Alex Bligh
2016-09-24 16:31 ` Alex Bligh
2016-09-24 16:42 ` Vladimir Sementsov-Ogievskiy
2016-09-24 16:49 ` Alex Bligh
2016-09-24 17:13 ` Vladimir Sementsov-Ogievskiy
2016-09-24 17:32 ` Alex Bligh
2016-09-24 17:47 ` Vladimir Sementsov-Ogievskiy
2016-09-24 18:24 ` Alex Bligh
2016-09-24 20:19 ` Vladimir Sementsov-Ogievskiy
2016-09-24 22:30 ` Wouter Verhelst
2016-09-24 17:33 ` Vladimir Sementsov-Ogievskiy
2016-09-24 20:14 ` [Qemu-devel] [Nbd] " Carl-Daniel Hailfinger
2016-09-24 20:32 ` Vladimir Sementsov-Ogievskiy
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=20160926084715.GC6093@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=alex@alex.org.uk \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=nbd-general@lists.sourceforge.net \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
--cc=w@uter.be \
/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).