From: Eric Blake <eblake@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>,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] block/raw-posix: use seek_hole ahead of fiemap
Date: Fri, 26 Sep 2014 11:22:48 -0600 [thread overview]
Message-ID: <5425A0E8.2060405@redhat.com> (raw)
In-Reply-To: <1411686852-26487-2-git-send-email-tony@bakeyournoodle.com>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On 09/25/2014 05:14 PM, 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.
It also has the potential to be less precise than fiemap on older
kernels (any filesystem that supports fiemap but has not yet wired up
seek_hole will get the kernel's default fallback of claiming no holes at
all), but that problem will fade as more people use modern kernels.
This matches what coreutils does, so I like it on that grounds.
>
> 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
Thanks; it is indeed better.
>
> block/raw-posix.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-09-26 17:23 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
2014-09-26 17:22 ` Eric Blake [this message]
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=5425A0E8.2060405@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).