On Thu, 20 Jan 2011 10:48:33 +0800 Shaohua Li [off-list ref] wrote:

On Thu, 2011-01-20 at 10:42 +0800, Andrew Morton wrote:

quoted

On Thu, 20 Jan 2011 10:30:47 +0800 Shaohua Li [off-list ref] wrote:

quoted

quoted

I don't know if this is worth addressing.  Perhaps require that the
filp refers to the root of the fs?

I didn't see why this is needed, but I can limit the fip to the root of
the fs.

I don't think it matters much either.  The only problem I can see is if
we were to later try to extend the ioctl into a per-file thing.

since we return page range, a metadata page might be shared by several
files, which makes the per-file thing doesn't work. For a fs using
trees, it's even more hard to distinguish a file's metadata

hm, why.  A query for "which blocks need to be read to access this
file" may return blocks which are shared with other files, but it's
still useful info.  Because it will represent vastly less data (and
hence IO) than the current fs-wide thing.

Now I actually look at it, I cannot find any documentation for the ioctl!  

It seems to return a single offset/length tuple which refers to the
btrfs metadata "file", with the intent that this tuple later be fed
into a btrfs-specific readahead ioctl.

I can see how this might be used with say fatfs or ext3 where all
metadata resides within the blockdev address_space.  But how is a
filesytem which keeps its metadata in multiple address_spaces supposed
to use this interface?

So.  Please fully document the proposed userspace APIs!  This should be
the first thing we look at.  Then we can take a look at how applicable
that is to other-than-btrfs filesystems.