From: Rik van Riel <riel@nl.linux.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <ak@muc.de>,
ebiederm+eric@ccr.net, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org
Subject: Re: Q: PAGE_CACHE_SIZE?
Date: Tue, 25 May 1999 22:16:34 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.03.9905252213400.25857-100000@mirkwood.nl.linux.org> (raw)
In-Reply-To: <E10mK50-0001eC-00@the-village.bc.nu>
On Tue, 25 May 1999, Alan Cox wrote:
> > > 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, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-05-25 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-18 14:03 Eric W. Biederman
1999-05-18 15:04 ` Andi Kleen
1999-05-19 23:29 ` Chris Wedgwood
1999-05-20 17:12 ` Andrea Arcangeli
1999-05-25 16:29 ` Alan Cox
1999-05-25 20:16 ` Rik van Riel [this message]
1999-05-25 22:17 ` Matti Aarnio
1999-05-27 22:06 ` Alan Cox
1999-05-28 20:46 ` Stephen C. Tweedie
1999-05-28 21:33 ` Rik van Riel
1999-05-29 1:59 ` Stephen C. Tweedie
1999-05-30 23:12 ` Andrea Arcangeli
1999-06-01 0:01 ` Stephen C. Tweedie
1999-06-01 14:23 ` Andrea Arcangeli
1999-05-29 15:07 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.03.9905252213400.25857-100000@mirkwood.nl.linux.org \
--to=riel@nl.linux.org \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm+eric@ccr.net \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox