Nick's worst case scenario is already at least partially addressed by the=
=20
Lumpy Reclaim code in 2.6.23. His examples assume 2.6.22 or earlier=20
code.
The advantages of this approach over Andreas is basically that the 4k=20
filesystems still can be used as is. 4k is useful for binaries and for=20
text processing like used for compiles. Large Page sizes are useful for=20
file systems that contain large datasets (scientific data, multimedia=20
stuff, databases) for applications that depend on high I/O throughput.