From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: ralf@uni-koblenz.de
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: increasing page size
Date: Sun, 5 Jul 1998 20:04:33 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980705200308.1574J-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19980705145314.A1909@uni-koblenz.de>
On Sun, 5 Jul 1998 ralf@uni-koblenz.de wrote:
> On Sat, Jul 04, 1998 Rik van Riel wrote:
>
> > Page size is coded into hardware (except on m68k) and
> > there's no reason for using 32 kB pages when we can
> > use proper readahead and I/O clustering.
>
> Page size is selectable on a per page base on all MIPS CPUs. Possible
> sizes are 4kb, 16kb, 64kb, 256kb, 1mb, 4mb and 16mb. Since the number
> of TLB entries (64 on R3k family, 32 entries on R4300, 48 R4k, R5k)
> can become a performance limit for apps with a large working set, using
> larger pagesizes is desireable.
Hmm, would that be tunable on a per-application basis, or
maybe as a kernel compile time option?
(the per-application thingy would be nice so we could avoid
breakage of applications when we switch the page size of the
kernel)
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next parent reply other threads:[~1998-07-05 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980705145314.A1909@uni-koblenz.de>
1998-07-05 18:04 ` Rik van Riel [this message]
[not found] <Pine.LNX.3.95.980705212619.1514A-100000@localhost>
1998-07-06 6:41 ` Rik van Riel
[not found] <Pine.A41.3.95.980705101710.48492B-100000@stud2.tuwien.ac.at>
1998-07-05 11:29 ` Rik van Riel
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.3.96.980705200308.1574J-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.org \
--cc=ralf@uni-koblenz.de \
/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