From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, berto@igalia.com,
stefanha@redhat.com, pavel.dovgaluk@ispras.ru, sw@weilnetz.de,
pl@kamp.de, qemu-devel@nongnu.org, mreitz@redhat.com,
jsnow@redhat.com, ronniesahlberg@gmail.com, den@openvz.org,
pbonzini@redhat.com, dillaman@redhat.com, ari@tuxera.com
Subject: Re: [RFC 0/3] 64bit block-layer part I
Date: Wed, 22 Apr 2020 09:52:28 -0500 [thread overview]
Message-ID: <a900074d-149a-7311-9da9-600d32c874ee@redhat.com> (raw)
In-Reply-To: <572e78c6-f346-58e8-98cd-1b355e5bb33b@virtuozzo.com>
On 4/22/20 9:29 AM, Vladimir Sementsov-Ogievskiy wrote:
> Any thoughts here? I need to resend to update some more functions as
> patchew said.
>
> Is it OK in general? Or should we instead convert everything to uint64_t ?
I definitely prefer int64_t as our base (off_t is signed as well, making
63 bits an effective limit everywhere).
>
> 30.03.2020 17:18, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> There is an idea to make NBD protocol extension to support 64bit
>> write-zero/discard/block-status commands (commands, which doesn't
>> transfer user data). It's needed to increase performance of zeroing
>> large ranges (up to the whole image). Zeroing of the whole image is used
>> as first step of mirror job, qemu-img convert, it should be also used at
>> start of backup actually..
>>
>> We need to support it in block-layer, so we want 64bit write_zeros.
>> Currently driver handler now have int bytes parameter.
>>
>> write_zeros path goes through normal pwritev, so we need 64bit write,
>> and then we need 64bit read for symmetry, and better, let's make all io
>> path work with 64bit bytes parameter.
>>
>> Actually most of block-layer already have 64bit parameters: offset is
>> sometimes int64_t and sometimes uint64_t. bytes parameter is one of
>> int64_t, uint64_t, int, unsigned int...
>>
>> I think we need one type for all of this, and this one type is int64_t.
>> Signed int64_t is a bit better than uint64_t: you can use same variable
>> to get some result (including error < 0) and than reuse it as an
>> argument without any type conversion.
>>
>> So, I propose, as a first step, convert all uint64_t parameters to
>> int64_t.
Makes sense. I haven't looked at the series closely in part because it
was 5.1 material while we were still focused on getting 5.0 out the
door, but it is now raising in my review queue again.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-04-22 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 14:18 [RFC 0/3] 64bit block-layer part I Vladimir Sementsov-Ogievskiy
2020-03-30 14:18 ` [PATCH 1/3] block: use int64_t as bytes type in tracked requests Vladimir Sementsov-Ogievskiy
2020-04-22 15:37 ` Stefan Hajnoczi
2020-04-23 15:25 ` Kevin Wolf
2020-03-30 14:18 ` [PATCH 2/3] block/io: convert generic io path to use int64_t parameters Vladimir Sementsov-Ogievskiy
2020-04-22 15:50 ` Stefan Hajnoczi
2020-04-22 17:45 ` Vladimir Sementsov-Ogievskiy
2020-03-30 14:18 ` [PATCH 3/3] block: use int64_t instead of uint64_t in driver handlers Vladimir Sementsov-Ogievskiy
2020-03-30 17:43 ` [RFC 0/3] 64bit block-layer part I no-reply
2020-03-30 17:48 ` no-reply
2020-03-30 17:50 ` no-reply
2020-04-22 14:29 ` Vladimir Sementsov-Ogievskiy
2020-04-22 14:52 ` Eric Blake [this message]
2020-04-22 15:53 ` Stefan Hajnoczi
2020-04-22 18:24 ` Vladimir Sementsov-Ogievskiy
2020-04-22 19:32 ` Eric Blake
2020-04-23 15:43 ` Kevin Wolf
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=a900074d-149a-7311-9da9-600d32c874ee@redhat.com \
--to=eblake@redhat.com \
--cc=ari@tuxera.com \
--cc=berto@igalia.com \
--cc=den@openvz.org \
--cc=dillaman@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
--cc=vsementsov@virtuozzo.com \
/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).