From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Fam Zheng <famz@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/6] null: Switch to byte-based read/write
Date: Tue, 24 Apr 2018 12:40:06 -0500 [thread overview]
Message-ID: <1cee058b-465d-4862-7fb0-8567f79c79b1@redhat.com> (raw)
In-Reply-To: <20180424171920.GI4080@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
On 04/24/2018 12:19 PM, Kevin Wolf wrote:
>>>> +static void null_refresh_limits(BlockDriverState *bs, Error **errp)
>>>> +{
>>>> + bs->bl.request_alignment = 1;
>>>> +}
>>>
>>> I would rather modify bdrv_refresh_limits() so that it defaults to 1 for
>>> drivers supporting either .bdrv_co_preadv or .bdrv_aio_preadv.
>>
>> Sure, I can do that (although then I may have to provide a
>> refresh_limits callback for each of the other drivers that I
>> specifically left at 512 alignment).
>
> Do we know that the other drivers need 512, or do we expect than they
> can handle byte granularity, but we try to err on the safe side?
Done to err on the safe side and avoid the difficulty of a deep audit in
code I'm unfamiliar with; in fact, for vxhs, I wasn't even able to
compile test things, which means I certainly wasn't able to reproduce a
test to see if dropping the alignment would break anything under qemu-io.
>
> If it's the latter (which would be my expectation), then it's probably
> better to set request_alignment = 512 with a comment in those drivers
> and hope that someone will lift the restriction in the future.
Indeed, leaving a good comment for a future reader is worth the effort.
I'll send a v2 later today.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-04-24 17:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 19:28 [Qemu-devel] [PATCH 0/6] block: byte-based AIO read/write Eric Blake
2018-02-15 19:28 ` [Qemu-devel] [PATCH 1/6] block: Support byte-based aio callbacks Eric Blake
2018-04-24 15:40 ` Kevin Wolf
2018-04-24 17:06 ` Eric Blake
2018-04-24 17:15 ` Kevin Wolf
2018-04-24 19:16 ` Eric Blake
2018-02-15 19:28 ` [Qemu-devel] [PATCH 2/6] file-win32: Switch to byte-based callbacks Eric Blake
2018-02-15 19:28 ` [Qemu-devel] [PATCH 3/6] null: Switch to byte-based read/write Eric Blake
2018-04-24 15:52 ` Kevin Wolf
2018-04-24 17:00 ` Eric Blake
2018-04-24 17:19 ` Kevin Wolf
2018-04-24 17:40 ` Eric Blake [this message]
2018-02-15 19:28 ` [Qemu-devel] [PATCH 4/6] rbd: Switch to byte-based callbacks Eric Blake
2018-02-15 19:28 ` [Qemu-devel] [PATCH 5/6] vxhs: " Eric Blake
2018-02-15 19:28 ` [Qemu-devel] [PATCH 6/6] block: Drop last of the sector-based aio callbacks Eric Blake
2018-04-24 15:02 ` [Qemu-devel] [PATCH 0/6] block: byte-based AIO read/write Eric Blake
2018-04-24 19:13 ` John Snow
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=1cee058b-465d-4862-7fb0-8567f79c79b1@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).