From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Andreas Dilger <adilger@sun.com>,
Eric Sandeen <esandeen@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3] Fiemap, an extent mapping ioctl
Date: Wed, 10 Sep 2008 11:46:12 -0700 [thread overview]
Message-ID: <20080910114612.314978a8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080910124934.GB4563@wotan.suse.de>
On Wed, 10 Sep 2008 05:49:34 -0700 Mark Fasheh <mfasheh@suse.com> wrote:
> Hello,
>
> The following patches are the latest attempt at implementing a
> fiemap ioctl, which can be used by userspace software to get extent
> information for an inode in an efficient manner.
As these are applicable to all filesystems, Cc:ing only linux-ext4 is
not sufficient. All filesystem developers (at least) need an
opportunity to review and understand these changes.
>
> ...
>
> The fiemap ioctl is an efficient method for userspace to get file
> extent mappings. Instead of block-by-block mapping (such as bmap), fiemap
> returns a list of extents.
>
The above is, afacit, the only offered rationale for the addition of
these new feature. I don't recall seeing anyone complain about bmap()
inefficiency. In fact I rarely hear of anyone using bmap() at all.
This rationale needs expanding, please. A lot.
next prev parent reply other threads:[~2008-09-10 18:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 20:22 FIEMAP patches Andreas Dilger
2008-08-26 6:22 ` Mark Fasheh
2008-08-26 6:57 ` Andreas Dilger
2008-09-10 12:40 ` Mark Fasheh
2008-09-10 12:49 ` [PATCH 0/3] Fiemap, an extent mapping ioctl Mark Fasheh
2008-09-10 13:47 ` Christoph Hellwig
2008-09-10 14:07 ` Theodore Tso
2008-09-10 14:11 ` Christoph Hellwig
2008-09-10 20:33 ` Andreas Dilger
2008-09-10 16:10 ` Mark Fasheh
2008-09-10 16:20 ` Christoph Hellwig
2008-09-10 18:46 ` Andrew Morton [this message]
2008-09-10 19:46 ` Andreas Dilger
2008-09-10 12:49 ` [PATCH 1/3] vfs: vfs-level fiemap interface Mark Fasheh
2008-09-10 12:50 ` [PATCH 2/3] generic block based fiemap implementation Mark Fasheh
2008-09-10 12:50 ` [PATCH 3/3] ocfs2: fiemap support Mark Fasheh
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=20080910114612.314978a8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adilger@sun.com \
--cc=esandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mfasheh@suse.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