From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Peter-Paul Witta <e9525748@student.tuwien.ac.at>
Cc: "David S. Miller" <davem@dm.cobaltmicro.com>,
Linux MM <linux-mm@kvack.org>
Subject: Re: increasing page size
Date: Sun, 5 Jul 1998 13:29:58 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980705132841.960B-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.A41.3.95.980705101710.48492B-100000@stud2.tuwien.ac.at>
On Sun, 5 Jul 1998, Peter-Paul Witta wrote:
> > Stephen Tweedie and Ingo Molnar have some swapin
> > readahead code, carefully hidden in a secret place...
>
> this wont solve the dma fragmentation problem, would it???
That is solved with a new memory allocator. See my home
page for more info.
> > 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.
>
> i thought intel ia32 had no problems with 4k .. 4m ???
x86 uses 4k for user pages. The 4M pages only work for
ring-0 (kernel mode) stuff.
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 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.A41.3.95.980705101710.48492B-100000@stud2.tuwien.ac.at>
1998-07-05 11:29 ` Rik van Riel [this message]
[not found] <19980705145314.A1909@uni-koblenz.de>
1998-07-05 18:04 ` Rik van Riel
[not found] <Pine.LNX.3.95.980705212619.1514A-100000@localhost>
1998-07-06 6:41 ` 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.980705132841.960B-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=davem@dm.cobaltmicro.com \
--cc=e9525748@student.tuwien.ac.at \
--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