From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: berto@igalia.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v5 1/9] block: Add flags to BlockDriver.bdrv_co_truncate()
Date: Thu, 23 Apr 2020 14:42:17 +0200 [thread overview]
Message-ID: <20200423124217.GA7687@linux.fritz.box> (raw)
In-Reply-To: <f867217d-c202-5d5b-7fb4-ca68e6553265@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
Am 23.04.2020 um 11:41 hat Max Reitz geschrieben:
> On 22.04.20 17:21, Kevin Wolf wrote:
> > This adds a new BdrvRequestFlags parameter to the .bdrv_co_truncate()
> > driver callbacks, and a supported_truncate_flags field in
> > BlockDriverState that allows drivers to advertise support for request
> > flags in the context of truncate.
> >
> > For now, we always pass 0 and no drivers declare support for any flag.
> >
> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> > Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> > Reviewed-by: Alberto Garcia <berto@igalia.com>
> > ---
> > include/block/block_int.h | 10 +++++++++-
> > block/crypto.c | 3 ++-
> > block/file-posix.c | 2 +-
> > block/file-win32.c | 2 +-
> > block/gluster.c | 1 +
> > block/io.c | 8 +++++++-
> > block/iscsi.c | 2 +-
> > block/nfs.c | 3 ++-
> > block/qcow2.c | 2 +-
> > block/qed.c | 1 +
> > block/raw-format.c | 2 +-
> > block/rbd.c | 1 +
> > block/sheepdog.c | 4 ++--
> > block/ssh.c | 2 +-
> > tests/test-block-iothread.c | 3 ++-
> > 15 files changed, 33 insertions(+), 13 deletions(-)
>
> (I know I haven’t complained before, so *shrug*, but I wonder now
> whether it actually makes sense to have the same BdrvRequestFlags for
> all request types. Or why we have the same flags type for read, write,
> and zero-write already.)
Yeah, nothing this series introduces. I wonder, too, but as long as we
have enough bits to cover flags for all request types, and because we
have overlaps between the request types, it might be easier to have only
one set of flags. So it might be accidental, but I actually feel the
current state isn't bad.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-23 12:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:21 [PATCH v5 0/9] block: Fix resize (extending) of short overlays Kevin Wolf
2020-04-22 15:21 ` [PATCH v5 1/9] block: Add flags to BlockDriver.bdrv_co_truncate() Kevin Wolf
2020-04-23 9:41 ` Max Reitz
2020-04-23 12:42 ` Kevin Wolf [this message]
2020-04-22 15:21 ` [PATCH v5 2/9] block: Add flags to bdrv(_co)_truncate() Kevin Wolf
2020-04-23 10:04 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 3/9] block-backend: Add flags to blk_truncate() Kevin Wolf
2020-04-23 10:34 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 4/9] qcow2: Support BDRV_REQ_ZERO_WRITE for truncate Kevin Wolf
2020-04-22 15:33 ` Eric Blake
2020-04-22 15:58 ` Kevin Wolf
2020-04-22 16:14 ` Eric Blake
2020-04-23 13:23 ` Kevin Wolf
2020-04-23 13:59 ` Eric Blake
2020-04-23 10:53 ` Max Reitz
2020-04-23 13:25 ` Kevin Wolf
2020-04-23 13:56 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 5/9] raw-format: " Kevin Wolf
2020-04-22 15:34 ` Eric Blake
2020-04-23 10:54 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 6/9] file-posix: " Kevin Wolf
2020-04-23 10:57 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 7/9] block: truncate: Don't make backing file data visible Kevin Wolf
2020-04-23 11:14 ` Max Reitz
2020-04-23 13:00 ` Kevin Wolf
2020-04-22 15:21 ` [PATCH v5 8/9] iotests: Filter testfiles out in filter_img_info() Kevin Wolf
2020-04-23 11:24 ` Max Reitz
2020-04-22 15:21 ` [PATCH v5 9/9] iotests: Test committing to short backing file Kevin Wolf
2020-04-23 11:53 ` Max Reitz
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=20200423124217.GA7687@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).