> > > Who's idea was it start the work to make the granularity of the page
> > > cache larger?
> >
> > I guess the main motivation comes from the ARM port, where some versions
> > have PAGE_SIZE=32k.
>
> For large amounts of memory on fast boxes you want a higher page
> size. Some vendors even pick page size based on memory size at
> boot up.
This sounds suspiciously like the 'larger-blocks-for-larger-FSes'
tactic other systems have been using to hide the bad scalability
of their algorithms.
A larger page size is no compensation for the lack of a decent
read-{ahead,back,anywhere} I/O clustering algorithm in the OS.
I believe we should take the more appropriate path and build
a proper 'smart' algorithm. Once we're optimizing for I/O
minimization, CPU is relatively cheap anyway...
Rik -- Open Source: you deserve to be in control of your data.
+-------------------------------------------------------------------+
| Le Reseau netwerksystemen BV: http://www.reseau.nl/ |
| Linux Memory Management site: http://www.linux.eu.org/Linux-MM/ |
| Nederlandse Linux documentatie: http://www.nl.linux.org/ |
+-------------------------------------------------------------------+
-
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/