linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
	linuxppc-dev@lists.ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] powerpc: Set a smaller value for RECLAIM_DISTANCE to enable zone reclaim
Date: Fri, 19 Feb 2010 09:51:12 -0600 (CST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1002190948200.26567@router.home> (raw)
In-Reply-To: <661de9471002190741k34ddb1acidf64d089bf9ff284@mail.gmail.com>

On Fri, 19 Feb 2010, Balbir Singh wrote:

> >> zone_reclaim. The others back off and try the next zone in the zonelist
> >> instead. I'm not sure what the original intention was but most likely it
> >> was to prevent too many parallel reclaimers in the same zone potentially
> >> dumping out way more data than necessary.
> >
> > Yes it was to prevent concurrency slowing down reclaim. At that time the
> > number of processors per NUMA node was 2 or so. The number of pages that
> > are reclaimed is limited to avoid tossing too many page cache pages.
> >
>
> That is interesting, I always thought it was to try and free page
> cache first. For example with zone->min_unmapped_pages, if
> zone_pagecache_reclaimable is greater than unmapped pages, we start
> reclaim the cached pages first. The min_unmapped_pages almost sounds
> like the higher level watermark - or am I misreading the code.

Indeed the purpose is to free *old* page cache pages.

The min_unmapped_pages is to protect a mininum of the page cache pages /
fs metadata from zone reclaim so that ongoing file I/O is not impacted.

  reply	other threads:[~2010-02-19 15:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 22:29 [PATCH] powerpc: Set a smaller value for RECLAIM_DISTANCE to enable zone reclaim Anton Blanchard
2010-02-19  0:07 ` Anton Blanchard
2010-02-19 14:55   ` Mel Gorman
2010-02-19 15:12     ` Christoph Lameter
2010-02-19 15:41       ` Balbir Singh
2010-02-19 15:51         ` Christoph Lameter [this message]
2010-02-19 17:39           ` Balbir Singh
2010-02-23  1:55     ` Anton Blanchard
2010-02-23 16:23       ` Mel Gorman
2010-02-24 15:43       ` Christoph Lameter
2010-03-01 12:06       ` Mel Gorman
2010-03-01 15:19         ` Christoph Lameter
2010-02-19 15:43 ` Balbir Singh
2010-02-23  1:38   ` Anton Blanchard

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=alpine.DEB.2.00.1002190948200.26567@router.home \
    --to=cl@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mel@csn.ul.ie \
    /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;
as well as URLs for NNTP newsgroup(s).