linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Stephen C. Tweedie" <sct@dcs.ed.ac.uk>, linux-mm <linux-mm@kvack.org>
Subject: Re: new allocation algorithm
Date: Mon, 30 Mar 1998 17:07:47 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.LNX.3.91.980330170431.242H-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <Pine.LNX.3.95.980327092811.6613C-100000@penguin.transmeta.com>

On Fri, 27 Mar 1998, Linus Torvalds wrote:
> On Fri, 27 Mar 1998, Rik van Riel wrote:
> > 
> > I just came up with the idea of using an ext2 like algorithm
> > for memory allocation, in which we:
> > - group memory in 128 PAGE groups
> > - have one unsigned char counter per group, counting the number
> >   of used pages
> 
> Let's wait with how well the current setup works. It seems to perform
> reasonably well even on smaller machines (modulo your patch), and I think
> we'd better more-or-less freeze it waiting for further info on what people
> actually think. 

At the moment, all that's freezing are the small-memory
machines :-(

> The current scheme is fairly efficient and extremely stable, and gives
> good behaviour for the cases we _really_ care about (pageorders 0, 1 and
> to some degree 2). It comes reasonably close to working for the higher
> orders too, but they really aren't as critical..

However, when we:
- allocate one page out of a 128 area
- we continue allocating pages out of that area, even when
- several 16k area's are freed and
- we are not able to free another large area again, so:
- the system swaps to death

This is not hypothetical, I've seen it happen :-(

Another way to do it, is to have machines exit with different
kswapd tests, as in:

if (num_physpages < arbitrary_limit && free_memory_available(2))
	break;

Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page          | Scouting       webmaster |
|        - kswapd ask-him & complain-to guy | Vries    cubscout leader |
|     http://www.fys.ruu.nl/~riel/          | <H.H.vanRiel@fys.ruu.nl> |
+-------------------------------------------+--------------------------+

  parent reply	other threads:[~1998-03-30 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-27  9:03 Rik van Riel
1998-03-27 17:30 ` Linus Torvalds
1998-03-27 18:33   ` Benjamin C.R. LaHaise
1998-03-30 15:07   ` Rik van Riel [this message]
1998-04-01 20:28   ` 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.91.980330170431.242H-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@fys.ruu.nl \
    --cc=linux-mm@kvack.org \
    --cc=sct@dcs.ed.ac.uk \
    --cc=torvalds@transmeta.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