Re: what is our answer to ZFS?

[Jörn Engel]

On Tue, 22 November 2005 07:51:48 +0000, Christoph Hellwig wrote:
> 
> > o 128 bit
> >   On 32bit machines, you can't even fully utilize a 64bit filesystem
> >   without VFS changes.  Have you ever noticed?  Thought so.
> 
> What is a '128 bit' or '64 bit' filesystem anyway?  This description doesn't
> make any sense,  as there are many different things that can be
> addresses in filesystems, and those can be addressed in different ways.
> I guess from the marketing documents that they do 128 bit _byte_ addressing
> for diskspace.  All the interesting Linux filesystems do _block_ addressing
> though, and 64bits addressing large enough blocks is quite huge.
> 128bit inodes again is something could couldn't easily implement, it would
> mean a non-scalar ino_t type which guarantees to break userspace.  128
> i_size?  Again that would totally break userspace because it expects off_t
> to be a scalar, so every single file must fit into 64bit _byte_ addressing.
> If the surrounding enviroment changes (e.g. we get a 128bit scalar type
> on 64bit architectures) that could change pretty easily, similarly to how
> ext2 got a 64bit i_size during the 2.3.x LFS work.

...once the need arises.  Even with byte addressing, 64 bit are enough
to handle roughly 46116860 of the biggest hard disks currently
available.  Looks like we still have a bit of time to think about the
problem before action is required.

Jörn

-- 
Victory in war is not repetitious.
-- Sun Tzu
-
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/