From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] Zone reclaim: Allow modification of zone reclaim behavior
Date: Mon, 30 Jan 2006 13:45:54 -0800 [thread overview]
Message-ID: <20060130134554.500b73a3.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0601301223350.4821@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@engr.sgi.com> wrote:
>
> In some situations one may want zone_reclaim to behave differently. For
> example a process writing large amounts of memory will spew unto other
> nodes to cache the writes if many pages in a zone become dirty. This may
> impact the performance of processes running on other nodes.
>
> Allowing writes during reclaim puts a stop to that behavior and throttles
> the process by restricting the pages to the local zone.
>
> Similarly one may want to contain processes to local memory by enabling
> regular swap behavior during zone_reclaim. Off node memory allocation
> can then be controlled through memory policies and cpusets.
The proliferating /proc configurability is a worry. It'll confuse people
and people just won't know that it's there and it's yet another question
which maintenance people need to ask end-users during problem resolution.
Is there not some means by which we can simply get these things right?
Why wouldn't we want to perform writeback or swapout during zone reclaim?
Why wouldn't we want to reclaim slab during zone reclaim?
--
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.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-01-30 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 20:24 Christoph Lameter
2006-01-30 21:45 ` Andrew Morton [this message]
2006-01-30 21:59 ` Christoph Lameter
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=20060130134554.500b73a3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--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