Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave Chinner wrote:
> On Fri, Jun 27, 2008 at 10:41:56AM +0100, Jamie Lokier wrote:
> > > > Right now the interface seems to be about returning details of the
> > > > filesystem's accounting of the on-disk layout, as opposed to just a
> > > > simple mapping.  As 2 examples:
...
> >    - The filesystem's internal representation may have _many_ more
> >      extents than the contiguous layout.  E.g. a 4GiB file might have
> >      65536 x 64kiB extents on some filesystem, or 1 extent when
> >      merged.  Is it ever useful to return the much larger list?
> 
> 64k max extent size? I'd consider that a block based filesystem,
> not an extent based filesytem....

It's only block based if the size is fixed.

Besides it's just an example.  If "real" extent based filesystems
never split their contiguous file extents for internal processing
reasons, I don't know what we're talking about :-)

-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux