From: Max Reitz <mreitz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, tony@bakeyournoodle.com,
stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/4] raw-posix: Clean up around raw_co_get_block_status()
Date: Thu, 13 Nov 2014 11:27:29 +0100 [thread overview]
Message-ID: <54648791.5010302@redhat.com> (raw)
In-Reply-To: <1415873823-13844-5-git-send-email-armbru@redhat.com>
On 2014-11-13 at 11:17, Markus Armbruster wrote:
> try_seek_hole() doesn't really seek to a hole, it tries to find out
> whether its argument is in a hole or not, and where the hole or
> non-hole ends. Rename to find_allocation() and add a proper function
> comment.
>
> Using arguments passed by reference like local variables is a bad
> habit. Only assign to them right before return.
>
> Avoid nesting of conditionals.
>
> When find_allocation() fails, don't make up a range that'll get mapped
> to nb_sectors, simply set *pnum = nb_sectors directly.
>
> Don't repeat BDRV_BLOCK_OFFSET_VALID | start.
>
> Drop a pointless assertion, add some meaningful ones.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> block/raw-posix.c | 62 +++++++++++++++++++++++++++++++++----------------------
> 1 file changed, 37 insertions(+), 25 deletions(-)
>
> diff --git a/block/raw-posix.c b/block/raw-posix.c
> index 2a12a50..ea5b3b8 100644
> --- a/block/raw-posix.c
> +++ b/block/raw-posix.c
> @@ -1478,28 +1478,43 @@ out:
> return result;
> }
>
> -static int try_seek_hole(BlockDriverState *bs, off_t start, off_t *data,
> - off_t *hole)
> +/*
> + * Find allocation range in @bs around offset @start.
> + * If @start is in a hole, store @start in @hole and the end of the
> + * hole in @data, and return 0.
> + * If @start is in a data, store @start to @data, and the end of the
"is in a data" sounds funny enough I'd even like to keep it. Probably
should be "data extent" or something similar.
> + * data to @hole, and return 0.
Here, too.
With or without that changed:
Reviewed-by: Max Reitz <mreitz@redhat.com>
next prev parent reply other threads:[~2014-11-13 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 10:16 [Qemu-devel] [PATCH v2 0/4] raw-posix: Get rid of FIEMAP, and more Markus Armbruster
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 1/4] raw-posix: Fix comment for raw_co_get_block_status() Markus Armbruster
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 2/4] raw-posix: SEEK_HOLE suffices, get rid of FIEMAP Markus Armbruster
2014-11-13 10:19 ` Max Reitz
2014-11-13 14:09 ` Eric Blake
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 3/4] raw-posix: Fix try_seek_hole()'s handling of SEEK_DATA failure Markus Armbruster
2014-11-13 10:22 ` Max Reitz
2014-11-13 13:03 ` Kevin Wolf
2014-11-13 14:52 ` Eric Blake
2014-11-13 15:29 ` Eric Blake
2014-11-13 15:44 ` Max Reitz
2014-11-13 15:49 ` Eric Blake
2014-11-13 15:52 ` Eric Blake
2014-11-13 15:47 ` Eric Blake
2014-11-13 16:01 ` Eric Blake
2014-11-14 13:12 ` Markus Armbruster
2014-11-15 0:47 ` Eric Blake
2014-11-13 10:17 ` [Qemu-devel] [PATCH v2 4/4] raw-posix: Clean up around raw_co_get_block_status() Markus Armbruster
2014-11-13 10:27 ` Max Reitz [this message]
2014-11-13 12:48 ` Markus Armbruster
2014-11-13 13:30 ` [Qemu-devel] [PATCH v2 0/4] raw-posix: Get rid of FIEMAP, and more 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=54648791.5010302@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tony@bakeyournoodle.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).