Messages in this thread | | | Subject | Re: Q: PAGE_CACHE_SIZE? | Date | Wed, 26 May 1999 01:17:53 +0300 (EEST) | From | Matti Aarnio <> |
| |
Rik van Riel <riel@nl.linux.org> wrote: ... > This sounds suspiciously like the 'larger-blocks-for-larger-FSes' > tactic other systems have been using to hide the bad scalability > of their algorithms. ... (read-ahead comments cut away) ...
I have this following table about EXT2 (and UFS, and SysVfs, and..) filesystem maximum supported file size. These limits stem from block addressability limitations in the classical tripply-indirection schemes:
Block Size File Size
512 2 GB + epsilon 1k 16 GB + epsilon 2k 128 GB + epsilon 4k 1024 GB + epsilon 8k 8192 GB + epsilon ( not without PAGE_SIZE >= 8 kB )
And of course any single partition filesystem in Linux (all of the 'local devices' filesystems right now) can't exceed 4G blocks of 512 bytes which limit is at the block device layer. (This gives maximum physical filesystem size of 2 TB for EXT2.)
So, in my opinnion any triply-indirected filesystem is at the end of its life when it comes to truly massive datasets.
The EXT2FS family will soon get new ways to extend its life by having alternate block addressing structure to that of the classical triply- indirection scheme it now uses. (Ted Ts'o is working at it.)
> Rik -- Open Source: you deserve to be in control of your data.
/Matti Aarnio <matti.aarnio@sonera.fi>
- 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/
| |