linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@uni-koblenz.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rik van Riel <riel@nl.linux.org>,
	ak@muc.de, ebiederm+eric@ccr.net, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: Q: PAGE_CACHE_SIZE?
Date: Sat, 29 May 1999 17:07:12 +0200	[thread overview]
Message-ID: <19990529170712.D1517@uni-koblenz.de> (raw)
In-Reply-To: <14159.137.169623.500547@dukat.scot.redhat.com>; from Stephen C. Tweedie on Fri, May 28, 1999 at 09:46:01PM +0100

On Fri, May 28, 1999 at 09:46:01PM +0100, Stephen C. Tweedie wrote:


> If we did in fact use the 4k minipage for all kernel get_free_page()
> allocations as usual, but used the larger 32k buddy heap pages for all
> VM allocations, then 8K kernel allocations (eg. stack allocations and
> large NFS packets) become trivial to deal with.
> 
> The biggest problem we have had with these multi-page allocations up to
> now is fragmentation in the VM.  If we populate the _entire_ VM in
> multiples of 8k or more then we can never see such fragmentation at all.
> 8k might actually be a reasonable pagesize even on low memory machines:
> we found in 2.2 that the increased size of the kernel was compensated
> for by more efficient swapping so that things still went faster in low
> memory than under 2.2, and large pages may well have the same tradeoff.

I'm working on Linux/MIPS64 and I intend to cleanup the code such that the
kernel can be built for different page sizes.  I intend to benchmark
things for curiosity.  Maybe it's some viable system tuning option, even
though a compile time one.

  Ralf
--
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-29 23:40 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
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 [this message]

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=19990529170712.D1517@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --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 \
    --cc=riel@nl.linux.org \
    --cc=sct@redhat.com \
    /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