From: David Chinner <dgc@sgi.com>
To: linux-fsdevel@vger.kernel.org, David Chinner <dgc@sgi.com>,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com, hch@infradead.org,
Anton Altaparmakov <aia21@cam.ac.uk>,
Mike Waychison <mikew
Subject: Re: [RFC] add FIEMAP ioctl to efficiently map file allocation
Date: Tue, 30 Oct 2007 09:25:33 +1100 [thread overview]
Message-ID: <20071029222533.GO995458@sgi.com> (raw)
In-Reply-To: <20071029194507.GA8578@webber.adilger.int>
On Mon, Oct 29, 2007 at 01:45:07PM -0600, Andreas Dilger wrote:
> By request on #linuxfs, here is the FIEMAP spec that we used to implement
> the FIEMAP support for ext4. There was an ext4 patch posted on August 29
> to linux-ext4 entitled "[PATCH] FIEMAP ioctl".
Link:
http://marc.info/?l=linux-ext4&m=118838241209683&w=2
That's a very ext4 specific ioctl interface. Can we get this made
generic like the FIBMAP interface so we don't have to replicate all
the copyin/copyout handling and interface definitions everywhere?
i.e. a ->extent_map aops callout to the filesystem in generic code
just like ->bmap?
> I've asked Kalpak to post
> an updated version of that patch along with the changes to the "filefrag"
> tool to use FIEMAP.
Where can I find the test program that validates the implementation?
Also, following the fallocate model, can we get the interface definition
turned into a man page before anything is submitted upstream?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
WARNING: multiple messages have this Message-ID (diff)
From: David Chinner <dgc@sgi.com>
To: linux-fsdevel@vger.kernel.org, David Chinner <dgc@sgi.com>,
linux-ext4@vger.kernel.org, xfs@oss.sgi.com, hch@infradead.org,
Anton Altaparmakov <aia21@cam.ac.uk>,
Mike Waychison <mikew@google.com>
Subject: Re: [RFC] add FIEMAP ioctl to efficiently map file allocation
Date: Tue, 30 Oct 2007 09:25:33 +1100 [thread overview]
Message-ID: <20071029222533.GO995458@sgi.com> (raw)
In-Reply-To: <20071029194507.GA8578@webber.adilger.int>
On Mon, Oct 29, 2007 at 01:45:07PM -0600, Andreas Dilger wrote:
> By request on #linuxfs, here is the FIEMAP spec that we used to implement
> the FIEMAP support for ext4. There was an ext4 patch posted on August 29
> to linux-ext4 entitled "[PATCH] FIEMAP ioctl".
Link:
http://marc.info/?l=linux-ext4&m=118838241209683&w=2
That's a very ext4 specific ioctl interface. Can we get this made
generic like the FIBMAP interface so we don't have to replicate all
the copyin/copyout handling and interface definitions everywhere?
i.e. a ->extent_map aops callout to the filesystem in generic code
just like ->bmap?
> I've asked Kalpak to post
> an updated version of that patch along with the changes to the "filefrag"
> tool to use FIEMAP.
Where can I find the test program that validates the implementation?
Also, following the fallocate model, can we get the interface definition
turned into a man page before anything is submitted upstream?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-10-29 22:25 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 11:05 [RFC] add FIEMAP ioctl to efficiently map file allocation Andreas Dilger
2007-04-12 11:22 ` Anton Altaparmakov
2007-04-13 4:01 ` Andreas Dilger
2007-04-13 4:01 ` Andreas Dilger
2007-04-13 7:46 ` Anton Altaparmakov
2007-04-13 14:53 ` Jeff Mahoney
2007-04-13 1:33 ` Nicholas Miell
2007-04-13 10:15 ` Christoph Hellwig
2007-04-13 11:38 ` Anton Altaparmakov
2007-04-13 18:55 ` Nicholas Miell
2007-04-16 8:01 ` Timothy Shimmin
2007-04-18 23:03 ` Andreas Dilger
2007-04-16 11:22 ` David Chinner
2007-04-19 0:21 ` Andreas Dilger
2007-04-19 1:54 ` David Chinner
2007-04-30 22:44 ` Andreas Dilger
2007-05-01 4:22 ` David Chinner
2007-05-01 4:39 ` Nicholas Miell
2007-05-01 14:20 ` David Chinner
2007-05-01 18:46 ` Anton Altaparmakov
2007-05-02 9:15 ` David Chinner
2007-05-02 9:36 ` Anton Altaparmakov
2007-05-02 10:57 ` David Chinner
2007-05-02 11:17 ` Anton Altaparmakov
2007-05-03 7:49 ` Andreas Dilger
2007-05-03 8:23 ` Anton Altaparmakov
2007-05-02 9:45 ` Anton Altaparmakov
2007-05-01 22:32 ` Andreas Dilger
2007-05-01 18:37 ` Anton Altaparmakov
2007-05-02 0:06 ` David Chinner
2007-05-02 8:16 ` Anton Altaparmakov
2007-10-29 19:45 ` Andreas Dilger
2007-10-29 13:57 ` [Ocfs2-devel] " Mark Fasheh
2007-10-29 20:57 ` Mark Fasheh
2007-10-29 20:57 ` Mark Fasheh
2007-10-29 22:13 ` Andreas Dilger
2007-11-05 17:44 ` [Ocfs2-devel] " Andreas Dilger
2007-10-29 17:11 ` Mark Fasheh
2007-10-30 0:11 ` Mark Fasheh
2007-10-30 0:11 ` Mark Fasheh
2007-10-30 0:25 ` Andreas Dilger
2007-11-05 17:44 ` [Ocfs2-devel] " Andreas Dilger
2007-10-29 22:29 ` Andreas Dilger
2007-11-05 17:44 ` [Ocfs2-devel] " Andreas Dilger
2007-10-29 22:29 ` Andreas Dilger
2007-10-29 15:40 ` [Ocfs2-devel] " Mark Fasheh
2007-10-29 22:40 ` Mark Fasheh
2007-10-29 22:40 ` Mark Fasheh
2007-10-29 22:25 ` David Chinner [this message]
2007-10-29 22:25 ` David Chinner
2007-05-01 22:30 ` Andreas Dilger
2007-05-02 2:26 ` David Chinner
2007-05-02 8:23 ` Anton Altaparmakov
2007-05-02 8:30 ` Anton Altaparmakov
2007-05-02 9:48 ` David Chinner
2007-05-02 9:56 ` Anton Altaparmakov
2007-04-19 6:23 ` Timothy Shimmin
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=20071029222533.GO995458@sgi.com \
--to=dgc@sgi.com \
--cc=aia21@cam.ac.uk \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.