From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, Fam Zheng <fam@euphon.net>,
integration@gluster.org, Alberto Garcia <berto@igalia.com>,
Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>,
qemu-block@nongnu.org, Jason Dillaman <dillaman@redhat.com>,
Stefan Weil <sw@weilnetz.de>, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
Liu Yuan <namei.unix@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
Ari Sundholm <ari@tuxera.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [PATCH v5 00/11] 64bit block-layer: part II
Date: Fri, 4 Jun 2021 13:30:31 -0500 [thread overview]
Message-ID: <20210604183031.kvwotfxtxmlkq32m@redhat.com> (raw)
In-Reply-To: <20210505075001.45041-1-vsementsov@virtuozzo.com>
On Wed, May 05, 2021 at 10:49:50AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> v5: rebase on master, fix block comments style and over-80 line.
> 01: s/{}/()/ in subject, so that email not to be mangled.
Don't worry too much about that; if it happens again on v6, I can
manually fix the commit on my side or else pull the commit directly
from your repo (if you provide a link) rather than via 'git am'
through the mailing list.
>
> part II aims to update block drivers to int64_t.
>
> I remind that main aim of this update of the whole block-layer to 64bit
> is to implement 64bit write-zeroes NBD request.
>
> Vladimir Sementsov-Ogievskiy (11):
I got through patches 1-6 in your v4 posting (our mails crossed), so
I'll assume those are similar, and resume my review with patch 7 in
this posting.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2021-06-04 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 7:49 [PATCH v5 00/11] 64bit block-layer: part II Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 01/11] block/io: bring request check to bdrv_co_(read, write)v_vmstate Vladimir Sementsov-Ogievskiy via
2021-05-05 7:49 ` [PATCH v5 02/11] qcow2: check request on vmstate save/load path Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 03/11] block: use int64_t instead of uint64_t in driver read handlers Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 04/11] block: use int64_t instead of uint64_t in driver write handlers Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 05/11] block: use int64_t instead of uint64_t in copy_range driver handlers Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 06/11] block: make BlockLimits::max_pwrite_zeroes 64bit Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 07/11] block: use int64_t instead of int in driver write_zeroes handlers Vladimir Sementsov-Ogievskiy
2021-06-04 20:09 ` Eric Blake
2021-06-05 13:50 ` Vladimir Sementsov-Ogievskiy
2021-05-05 7:49 ` [PATCH v5 08/11] block/io: allow 64bit write-zeroes requests Vladimir Sementsov-Ogievskiy
2021-06-07 15:03 ` Eric Blake
2021-05-05 7:49 ` [PATCH v5 09/11] block: make BlockLimits::max_pdiscard 64bit Vladimir Sementsov-Ogievskiy
2021-06-07 15:05 ` Eric Blake
2021-05-05 7:50 ` [PATCH v5 10/11] block: use int64_t instead of int in driver discard handlers Vladimir Sementsov-Ogievskiy
2021-06-07 18:13 ` Eric Blake
2021-06-08 8:38 ` Vladimir Sementsov-Ogievskiy
2021-05-05 7:50 ` [PATCH v5 11/11] block/io: allow 64bit discard requests Vladimir Sementsov-Ogievskiy
2021-06-07 18:15 ` Eric Blake
2021-05-05 8:06 ` [PATCH v5 00/11] 64bit block-layer: part II no-reply
2021-05-05 8:10 ` Vladimir Sementsov-Ogievskiy
2021-06-04 18:30 ` Eric Blake [this message]
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=20210604183031.kvwotfxtxmlkq32m@redhat.com \
--to=eblake@redhat.com \
--cc=ari@tuxera.com \
--cc=berto@igalia.com \
--cc=dillaman@redhat.com \
--cc=fam@euphon.net \
--cc=integration@gluster.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=namei.unix@gmail.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).