Re: [PATCH 06/10] AXFS: axfs_super.c

[Arnd Bergmann]

On Friday 22 August 2008, Phillip Lougher wrote:
> 1. Support for > 4GB filesystems. ÂIn theory 2^64 bytes.
> 2. Compressed metadata
> 3. Inode timestamps
> 4. Hard-link support, and correct nlink counts
> 5. Sparse file support
> 6. Support for ". & ".." in readdir
> 7. Indexed directories for fast lookup
> 8. NFS exporting
> 9. No need to cache entire metadata in memory
>
> Squashfs has been optimised for block-based rotating media like hard 
> disks, CDROMS. ÂAXFS has been optimised for flash based media. ÂSquashfs 
> will outperform AXFS on rotating media, AXFS will outperform Squashfs on 
> flash based media.

Ok, thanks for the list. I'm sure that sparse files are already
part of AXFS, and among the other things, I would consider some
to be AXFS bugs rather than squashfs features ("." in readdir, in
particular), but I get the point.

> Squashfs and AXFS should be seen as complementary filesystems, and there 
> should be room in the Linux kernel for both.
> 
> I don't see what your problem is here. ÂI think AXFS is an extremely 
> good filesystem and should be merged. ÂBut I don't see why this should 
> lead to more Squashfs bashing.

Sorry, I didn't mean to be abusive. From first look, it appeared to do
everything that squashfs does, with less code, but you've made it clear
that there is need for both of them.
I would still expect axfs to replace cramfs for all practical purposes,
even though that was written by our Emperor Penguin ;-)

	Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/