From: Max Reitz <mreitz@redhat.com>
To: Tony Breeds <tony@bakeyournoodle.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Pádraig Brady" <pbrady@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] block/raw-posix: use seek_hole ahead of fiemap
Date: Fri, 26 Sep 2014 19:04:47 +0200 [thread overview]
Message-ID: <54259CAF.6060904@redhat.com> (raw)
In-Reply-To: <1411686852-26487-2-git-send-email-tony@bakeyournoodle.com>
On 26.09.2014 01:14, Tony Breeds wrote:
> try_fiemap() uses FIEMAP_FLAG_SYNC which has a significant performance
> impact.
>
> Prefer seek_hole() over fiemap() to avoid this impact where possible.
> seek_hole is more widely used and, arguably, has potential to be
> optimised in the kernel.
>
> Reported-By: Michael Steffens <michael_steffens@posteo.de>
> Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Markus Armbruster <armbru@redhat.com>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> Cc: Max Reitz <mreitz@redhat.com>
> Cc: Pádraig Brady <pbrady@redhat.com>
> Cc: Eric Blake <eblake@redhat.com>
> ---
> Changes since v1:
> - split in to 2 patches
> - tried to make the commit messages better
I used this order in at least one of the non-final versions of 4f11aa8a,
so I'm fine with it. The reason it got rejected was (as far as I
remember) that the FIEMAP ioctl() returns ENOTSUP if not supported,
whereas lseek() with SEEK_HOLE/SEEK_DATA returns some failsafe value,
probably reporting no holes at all. By reversing the order of
try_fiemap() and try_seek_hole(), try_fiemap() therefore may very well
become dead code. I don't object, however.
Reviewed-by: Max Reitz <mreitz@redhat.com>
next prev parent reply other threads:[~2014-09-26 17:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 5:23 [Qemu-devel] [PATCH] block/raw-posix: use seek_hole ahead of fiemap Tony Breeds
2014-09-25 6:21 ` Markus Armbruster
2014-09-25 6:29 ` Tony Breeds
2014-09-25 6:42 ` Greg Kurz
2014-09-25 6:48 ` Tony Breeds
2014-09-25 6:47 ` Markus Armbruster
2014-09-25 7:30 ` Kevin Wolf
2014-09-25 9:00 ` Tony Breeds
2014-09-25 9:52 ` Kevin Wolf
2014-09-25 10:41 ` Pádraig Brady
2014-09-25 12:45 ` Eric Blake
2014-09-25 12:40 ` Eric Blake
2014-09-25 23:14 ` [Qemu-devel] [PATCH v2 1/2] block/raw-posix: Fix disk corruption in try_fiemap Tony Breeds
2014-09-25 23:14 ` [Qemu-devel] [PATCH v2 2/2] block/raw-posix: use seek_hole ahead of fiemap Tony Breeds
2014-09-26 17:04 ` Max Reitz [this message]
2014-09-26 17:22 ` Eric Blake
2014-09-26 17:05 ` [Qemu-devel] [PATCH v2 1/2] block/raw-posix: Fix disk corruption in try_fiemap Max Reitz
2014-09-26 17:09 ` Eric Blake
2014-09-26 22:15 ` Tony Breeds
2014-10-14 12:35 ` Kevin Wolf
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=54259CAF.6060904@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbrady@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).