From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: de-luxe zone allocator, design 2
Date: Wed, 29 Jul 1998 20:00:14 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980729195814.12136G-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <199807291104.MAA01217@dax.dcs.ed.ac.uk>
On Wed, 29 Jul 1998, Stephen C. Tweedie wrote:
> On Tue, 28 Jul 1998 18:15:41 +0200 (CEST), Rik van Riel
> <H.H.vanRiel@phys.uu.nl> said:
>
> > Agreed, although 16k chunks would probably be better for
> > 3 and 4 MB machines (allows DMA and network buffers).
>
> In 2.1.112 we've now chopped down the default slab size for large
> objects from 16k to 8k, so 8k should be OK. (8k NFS still needs 16k
> chunks, but you really want to be using 4k or smaller blocks on such
> low memory machines anyway, for precisely this reason.)
Isn't packing locality _very_ important on machines where you
have no memory to spare? In that case 16k would probably be
better; PLUS 16k will allow for real DMA buffers and stuff.
When we have lazy page reclamation, we don't have to keep free
the amount of pages we're keeping free now, so 16k areas should
be OK... (we'll only need to keep 2 of those free on most small
machines)
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 prev parent reply other threads:[~1998-07-29 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-24 21:03 Rik van Riel
1998-07-27 11:12 ` Stephen C. Tweedie
1998-07-28 16:15 ` Rik van Riel
1998-07-29 11:04 ` Stephen C. Tweedie
1998-07-29 18:00 ` Rik van Riel [this message]
1998-07-30 23:35 ` Stephen C. Tweedie
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.980729195814.12136G-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=linux-mm@kvack.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