From: Bob Peterson <rpeterso@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, Alexander Viro <aviro@redhat.com>,
cluster-devel <cluster-devel@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>
Subject: Re: [Cluster-devel] [PATCH][try6] VFS: new want_holesize and got_holesize buffer_head flags for fiemap
Date: Wed, 22 Oct 2014 08:28:53 -0400 (EDT) [thread overview]
Message-ID: <90509064.9314451.1413980933011.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20141022060434.GA11237@infradead.org>
----- Original Message -----
> This looks like a big indicator that get_blocks is the wrong
> interface for fiemap.
Hi Christoph,
Yes, I thought about that.
One of my early prototypes had a separate function used by fiemap.
Function __generic_block_fiemap would call get_block() which
returned an indication of a hole as it does today. When it saw
the hole, fiemap called a new function get_hole_size() that was
passed in like get_block. The problem is: it's grossly inefficient,
since the new function get_hole_size() has to redo most of the work
that get_block just did (at least in the case of GFS2). (Which in the
case of a 1PB sparse file is non-trivial, since it involves several
levels of metadata indirection). Combining it with get_block made it
much more efficient.
Making a separate get_block_map_fiemap() function just seems like an
exercise in redundancy.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2014-10-22 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <635673293.9099204.1413939501068.JavaMail.zimbra@redhat.com>
2014-10-22 1:09 ` [PATCH][try6] VFS: new want_holesize and got_holesize buffer_head flags for fiemap Bob Peterson
2014-10-22 6:04 ` [Cluster-devel] " Christoph Hellwig
2014-10-22 10:50 ` Steven Whitehouse
2014-10-22 12:28 ` Bob Peterson [this message]
2014-10-23 8:51 ` Christoph Hellwig
2014-10-23 12:34 ` Bob Peterson
2014-10-26 21:41 ` Dave Chinner
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=90509064.9314451.1413980933011.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=aviro@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=swhiteho@redhat.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).