From: "Jörn Engel" <joern@logfs.org>
To: Nicholas Miell <nmiell@comcast.net>
Cc: "Jörn Engel" <joern@logfs.org>,
"Andreas Dilger" <adilger@sun.com>,
"Josef Bacik" <jbacik@redhat.com>,
linux-fsdevel@vger.kernel.org,
"Andreas Dilger" <adilger@clusterfs.com>
Subject: Re: [RFC][PATCH] Implement SEEK_HOLE/SEEK_DATA
Date: Thu, 29 Nov 2007 04:07:59 +0100 [thread overview]
Message-ID: <20071129030758.GA11841@lazybastard.org> (raw)
In-Reply-To: <1196294785.18231.31.camel@entropy>
On Wed, 28 November 2007 16:06:25 -0800, Nicholas Miell wrote:
>
> I'd have to reread the original proposal, but I remember FIEMAP as being
> a generalized way of getting information about a files extents. I think
> the original proposal only dealt with mapping file offsets to physical
> extents, but IIRC the interface was flexible enough to implement a
> "where are the holes" request.
>
> Regardless, SEEK_HOLE/SEEK_DATA being a better suited interface for the
> needs of logfs doesn't make it the best interface for that need.
I'm not sure we are looking for the best interface. A significant
improvement without significant drawbacks would be enough for me.
Having to provide "physical extends" complete with device offsets would
be a significant drawback. Even if such an interface may have greater
advantages under ideal circumstances.
Jörn
--
He who knows others is wise.
He who knows himself is enlightened.
-- Lao Tsu
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-29 3:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 20:02 [RFC][PATCH] Implement SEEK_HOLE/SEEK_DATA Josef Bacik
2007-11-28 21:56 ` Brad Boyer
2007-11-28 23:38 ` Josef Bacik
2007-11-28 22:56 ` Nicholas Miell
2007-11-28 23:33 ` Josef Bacik
2007-11-28 23:50 ` Nicholas Miell
2007-11-28 23:39 ` Andreas Dilger
2007-11-28 23:48 ` Jörn Engel
2007-11-29 0:06 ` Nicholas Miell
2007-11-29 3:07 ` Jörn Engel [this message]
2007-11-29 3:27 ` Andreas Dilger
2007-11-29 4:14 ` Jörn Engel
2007-11-28 23:49 ` Andreas Dilger
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=20071129030758.GA11841@lazybastard.org \
--to=joern@logfs.org \
--cc=adilger@clusterfs.com \
--cc=adilger@sun.com \
--cc=jbacik@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nmiell@comcast.net \
/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).