public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, Christoph Hellwig <hch@infradead.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	ak@suse.de, torvalds@osdl.org
Subject: Re: [PATCH 1/2] Zone reclaim V2
Date: Tue, 06 Dec 2005 17:52:56 +0000	[thread overview]
Message-ID: <20051206175256.GO11190@wotan.suse.de> (raw)
In-Reply-To: <20051206172444.18786.30131.sendpatchset@schroedinger.engr.sgi.com>

On Tue, Dec 06, 2005 at 09:24:44AM -0800, Christoph Lameter wrote:
> Zone reclaim allows the reclaiming of pages from a zone if the number of free
> pages falls below the watermark even if other zones still have enough pages
> available. Zone reclaim is of particular importance for NUMA machines. It can
> be more beneficial to reclaim a page than taking the performance penalties
> that come with allocating a page on a remote zone.
> 
> The patch replaces Martin Hick's zone reclaim function (which was never
> working properly).
> 
> An arch can control zone_reclaim by setting zone_reclaim_mode during bootup
> if it is discovered that the kernel is running on an NUMA configuration.

Looks much better. Thanks. But how about auto controlling the variable in generic
code based on node_distance() (at least for the non node hotplug case)


> +/*
> + * Zone reclaim mode
> + *
> + * If non-zero call zone_reclaim when the number of free pages falls below
> + * the watermarks.
> + */
> +int zone_reclaim_mode;

I would mark it __read_mostly to avoid potential false sharing.

-Andi

  parent reply	other threads:[~2005-12-06 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 17:24 [PATCH 1/2] Zone reclaim V2 Christoph Lameter
2005-12-06 17:24 ` [PATCH 2/2] Remove debris from old zone reclaim Christoph Lameter
2005-12-06 17:52 ` Andi Kleen [this message]
2005-12-06 18:01   ` [PATCH 1/2] Zone reclaim V2 Christoph Lameter
2005-12-06 18:09     ` Andi Kleen
2005-12-06 18:41       ` 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=20051206175256.GO11190@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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