> : > If you have 200 small files and you have to go get 200 inodes and
> : > 200 blocks to read them in, the inodes and the blocks aren't next to
> : > each other, that's 400 disk transactions instead of 1.
> :
> : OK, so please explain the scale of what you have in mind. How big is
> : the compressed tarball, and how big is it uncompressed?
> :
> : Do you plan on having a large FS (say /usr) stored in this way, or are
> : you thinking of a selected subset?
>
> Do it on a per directory basis, only for files where links == 1.
Yes, sir? What will you do on link()? rename()?
> I wouldn't bother to compress - just putting all the files into a ``tarball''
> will compress them quite nicely because of the lack of fragmentation.
Until you'll start to do any namespace-modifying operations. Or simply
to change the length of files in question.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/