lkml.org 
[lkml]   [2001]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*}
Jussi Laako wrote:
>
> Daniel Phillips wrote:
> >
> > We are not that far away from being able to handle 8K blocks, so that
> > would bump it up to 32 TB.
>
> That's way too small. Something like 32 PB would be better... ;)
> We need at least one extra bit in volume/file size every year.
>
> - Jussi Laako
>
> --
> PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
> Available at PGP keyservers
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/


Daniel, if I was real sure that 64k blocks were the right answer, I would agree with you. I think
nobody knows what will happen with reiserfs if we go to 64k blocks. It could be great. On the
other hand, the average number of bytes memcopied with every small file insertion increases with
node size. Scalable integers (Xanadu project idea in which the last bit of an integer indicates
whether the integer is longer than the base size by an amount equal to the base size, chain can be
infinitely long, they used a base size of 1 byte, but we could use a base size of 32 bits, and limit
it to 64 bits rather than allowing infinite scaling) seem like more conservative coding.

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

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.071 / U:3.580 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site