linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@nl.linux.org>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
	torvalds@transmeta.com, mingo@chiara.csoma.elte.hu,
	linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: [RFC] [RFT] [PATCH] memory zone balancing
Date: Tue, 4 Jan 2000 04:23:31 +0100	[thread overview]
Message-ID: <Pine.LNX.4.10.10001040417340.654-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <200001040227.SAA98076@google.engr.sgi.com>

On Mon, 3 Jan 100, Kanoj Sarcar wrote:

> Okay, here is a reworked version. Note that this version does not
> do per-zone balancing, since experiments show that we need to tune
> per-zone watermarks properly before we can start doing that. I am 
> working on coming up with a good estimate of per-zone watermarks.
> Basically, I am trying to answer the question: if there are d dmapages,
> r regular pages and h highmem pages, for a total of d+r+h pages, 
> what should the watermarks be for each zone?

d+r+h > limit
d     > limit/2
r     > limit/4
h     > limit/8

DMA pages should always be present, regular pages for
storing pagetables and stuff need to be there too, higmem
pages we don't really care about.

Btw, I think we probably want to increase freepages.min
to 512 or even more on machines that have >1GB of memory.
The current limit of 256 was really intended for machines
with a single zone of memory...

(but on <1GB machines I don't know if it makes sense to
raise the limit much more ... maybe we should raise the
limit automagically if the page alloc/io rate is too
high?)

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.nl.linux.org/Linux-MM/

  reply	other threads:[~2000-01-04  3:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15 19:50 Kanoj Sarcar
1999-12-17  7:27 ` Mike Galbraith
1999-12-27 16:00   ` Andrea Arcangeli
1999-12-27 16:06 ` Andrea Arcangeli
2000-01-04  2:27   ` Kanoj Sarcar
2000-01-04  3:23     ` Rik van Riel [this message]
2000-01-04 15:47       ` Rik van Riel
2000-01-06 16:05     ` Ingo Molnar
2000-01-06 15:28       ` David S. Miller
2000-01-06 18:36         ` Kanoj Sarcar
2000-01-06 19:14         ` Rik van Riel
2000-01-04 19:42 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.4.10.10001040417340.654-100000@mirkwood.dummy.home \
    --to=riel@nl.linux.org \
    --cc=andrea@suse.de \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@chiara.csoma.elte.hu \
    --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