From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH][try6] VFS: new want_holesize and got_holesize buffer_head flags for fiemap
Date: Wed, 22 Oct 2014 11:50:39 +0100 [thread overview]
Message-ID: <54478BFF.8070608@redhat.com> (raw)
In-Reply-To: <20141022060434.GA11237@infradead.org>
Hi,
On 22/10/14 07:04, Christoph Hellwig wrote:
> This looks like a big indicator that get_blocks is the wrong
> interface for fiemap.
>
The question is then, what a better interface would look like? We could
have "get_hole" as an extra operation I suppose. Not sure that I really
see why thats better or worse than the extra flag at the moment? or did
you have something else in mind?
Steve.
next prev parent reply other threads:[~2014-10-22 10:50 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 ` [Cluster-devel] [PATCH][try6] VFS: new want_holesize and got_holesize buffer_head flags for fiemap Bob Peterson
2014-10-22 6:04 ` Christoph Hellwig
2014-10-22 10:50 ` Steven Whitehouse [this message]
2014-10-22 12:28 ` Bob Peterson
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=54478BFF.8070608@redhat.com \
--to=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).