From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>
Subject: Re: cpusets: only wakeup kswapd for zones in the current cpuset
Date: Mon, 22 May 2006 18:23:56 -0700 [thread overview]
Message-ID: <20060522182356.fbea4aec.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602081010440.2648@schroedinger.engr.sgi.com>
Three months ago, Christoph wrote:
> If we get under some memory pressure in a cpuset (we only scan zones
> that are in the cpuset for memory) then kswapd is woken
> up for all zones. This patch only wakes up kswapd in zones that are
> part of the current cpuset.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> Index: linux-2.6.16-rc2/mm/page_alloc.c
> ===================================================================
> --- linux-2.6.16-rc2.orig/mm/page_alloc.c 2006-02-02 22:03:08.000000000 -0800
> +++ linux-2.6.16-rc2/mm/page_alloc.c 2006-02-08 00:05:09.000000000 -0800
> @@ -923,7 +923,8 @@ restart:
> goto got_pg;
>
> do {
> - wakeup_kswapd(*z, order);
> + if (cpuset_zone_allowed(*z, gfp_mask))
> + wakeup_kswapd(*z, order);
> } while (*(++z));
>
> /*
>
Christoph,
Does this patch serve any use? Chris Wright just noticed (in private
email) that wakeup_kswapd() already contains a check for cpuset
confinement, so it would seem the above added check is superfluous.
Thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-05-23 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 18:11 cpusets: only wakeup kswapd for zones in the current cpuset Christoph Lameter
2006-05-23 1:23 ` Paul Jackson [this message]
2006-05-23 1:59 ` Christoph Lameter
2006-05-23 2:22 ` Paul Jackson
2006-05-23 2:28 ` Christoph Lameter
2006-05-23 6:35 ` [PATCH] cpuset: remove extra cpuset_zone_allowed check in __alloc_pages Chris Wright
2006-05-23 6:35 ` Paul Jackson
2006-05-23 16:29 ` Christoph Lameter
2006-05-23 16:38 ` Paul Jackson
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=20060522182356.fbea4aec.pj@sgi.com \
--to=pj@sgi.com \
--cc=chrisw@sous-sol.org \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.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