From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Alex Bligh <alex@alex.org.uk>
Cc: "nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>,
Kevin Wolf <kwolf@redhat.com>, qemu block <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Stefan stefanha@redhat. com" <stefanha@redhat.com>,
"Denis V. Lunev" <den@openvz.org>, Wouter Verhelst <w@uter.be>
Subject: Re: [Qemu-devel] [Nbd] write_zeroes/trim on the whole disk
Date: Sat, 24 Sep 2016 22:14:24 +0200 [thread overview]
Message-ID: <57E6DEA0.7050002@gmx.net> (raw)
In-Reply-To: <57E6B8CF.6040406@virtuozzo.com>
On 24.09.2016 19:33, Vladimir Sementsov-Ogievskiy wrote:
> On 24.09.2016 20:13, Vladimir Sementsov-Ogievskiy wrote:
>> I agree that requests larger than disk size are ugly.. But splitting
>> request brings me again to idea of having separate command or flag
>> for clearing the whole disk without that dance. Server may report
>> availability of this/flag command only if target driver supports fast
>> write_zeroes (qcow2 in our case).
> Also, such flag may be used to satisfy all needs:
>
> flag BIG_REQUEST is set and length = 0 -> request on the whole
> disk, offset must be 0
> flag BIG_REQUEST is set and length > 0 -> request on
> (offset*block_size, length*block_size), length*block_size must be <=
> disk_size
What happens if length*block_size<=disk_size, but
offset*block_size+length*block_size>disk_size? Wraparound?
Regards,
Carl-Daniel
next prev parent reply other threads:[~2016-09-24 20:15 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
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 ` Carl-Daniel Hailfinger [this message]
2016-09-24 20:32 ` [Qemu-devel] [Nbd] " 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=57E6DEA0.7050002@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=alex@alex.org.uk \
--cc=den@openvz.org \
--cc=kwolf@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).