linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Rik van Riel <riel@nl.linux.org>
Cc: alan@lxorguk.ukuu.org.uk, ak@muc.de, ebiederm+eric@ccr.net,
	linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Q: PAGE_CACHE_SIZE?
Date: Thu, 27 May 1999 23:06:48 +0100 (BST)	[thread overview]
Message-ID: <E10n8Ic-0003h9-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.03.9905252213400.25857-100000@mirkwood.nl.linux.org> from "Rik van Riel" at May 25, 99 10:16:34 pm

> A larger page size is no compensation for the lack of a decent
> read-{ahead,back,anywhere} I/O clustering algorithm in the OS.

It isnt compensating for that. If you have 4Gig of memory and a high performance
I/O controller the constant cost per page for VM management begins to dominate
the equation. Its also a win for other CPU related reasons (reduced tlb
misses and the like), and with 4Gig of RAM the argument is a larger page
size isnt a problem.

Alan

--
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/

  parent reply	other threads:[~1999-05-27 21:17 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
1999-05-25 22:17       ` Matti Aarnio
1999-05-27 22:06       ` Alan Cox [this message]
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=E10n8Ic-0003h9-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ak@muc.de \
    --cc=ebiederm+eric@ccr.net \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.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