From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, qemu-block@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 4/5] blkdebug: Add ability to override unmap geometries
Date: Wed, 7 Dec 2016 15:35:21 +0100 [thread overview]
Message-ID: <20161207143521.GF4773@noname.str.redhat.com> (raw)
In-Reply-To: <20161202192223.15153-5-eblake@redhat.com>
Am 02.12.2016 um 20:22 hat Eric Blake geschrieben:
> Make it easier to simulate various unusual hardware setups (for
> example, recent commits 3482b9b and b8d0a98 affect the Dell
> Equallogic iSCSI with its 15M preferred and maximum unmap and
> write zero sizing, or b2f95fe deals with the Linux loopback
> block device having a max_transfer of 64k), by allowing blkdebug
> to wrap any other device with further restrictions on various
> alignments.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
>
> ---
> v3: improve legibility of bounds checking, improve docs
> v2: new patch
> ---
> qapi/block-core.json | 27 ++++++++++++++-
> block/blkdebug.c | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++--
> 2 files changed, 120 insertions(+), 3 deletions(-)
>
> diff --git a/qapi/block-core.json b/qapi/block-core.json
> index c29bef7..26f3e9f 100644
> --- a/qapi/block-core.json
> +++ b/qapi/block-core.json
> @@ -2068,6 +2068,29 @@
> # @align: #optional required alignment for requests in bytes,
> # must be power of 2, or 0 for default
> #
> +# @max-transfer: #optional maximum size for I/O transfers in bytes,
> +# must be multiple of the larger of @align and and 512
s/and and/and/
> +# (but need not be a power of 2), or 0 for default
> +# (since 2.9)
What is the reason for the 512 bytes restriction? Not really a problem,
though, allowing more values later is easier than restricting them.
The rest looks good.
Kevin
next prev parent reply other threads:[~2016-12-07 14:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 19:22 [Qemu-devel] [PATCH v3 0/5] add blkdebug tests Eric Blake
2016-12-02 19:22 ` [Qemu-devel] [PATCH v3 1/5] blkdebug: Sanity check block layer guarantees Eric Blake
2016-12-06 21:26 ` Max Reitz
2016-12-07 16:17 ` Kevin Wolf
2016-12-02 19:22 ` [Qemu-devel] [PATCH v3 2/5] blkdebug: Add pass-through write_zero and discard support Eric Blake
2016-12-06 22:00 ` Max Reitz
2016-12-06 22:12 ` Eric Blake
2016-12-06 22:14 ` Max Reitz
2016-12-06 22:18 ` Eric Blake
2016-12-06 22:23 ` Max Reitz
2016-12-06 22:36 ` Eric Blake
2016-12-07 13:55 ` Kevin Wolf
2016-12-07 15:15 ` Eric Blake
2016-12-02 19:22 ` [Qemu-devel] [PATCH v3 3/5] blkdebug: Simplify override logic Eric Blake
2016-12-06 22:10 ` Max Reitz
2016-12-06 22:15 ` Eric Blake
2016-12-07 16:17 ` Kevin Wolf
2016-12-02 19:22 ` [Qemu-devel] [PATCH v3 4/5] blkdebug: Add ability to override unmap geometries Eric Blake
2016-12-06 22:31 ` Max Reitz
2016-12-07 14:35 ` Kevin Wolf [this message]
2016-12-07 15:11 ` Eric Blake
2016-12-02 19:22 ` [Qemu-devel] [PATCH v3 5/5] tests: Add coverage for recent block geometry fixes Eric Blake
2016-12-06 22:33 ` Max Reitz
2016-12-07 16:16 ` Kevin Wolf
2016-12-07 16:34 ` Eric Blake
2016-12-20 16:42 ` Eric Blake
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=20161207143521.GF4773@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@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).