From: Christoph Lameter <cl@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Rik van Riel <riel@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
yanmin.zhang@intel.com, Wu Fengguang <fengguang.wu@intel.com>,
linuxram@us.ibm.com, linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] Reintroduce zone_reclaim_interval for when zone_reclaim() scans and fails to avoid CPU spinning at 100% on NUMA
Date: Mon, 8 Jun 2009 10:55:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0906081055170.21954@gentwo.org> (raw)
In-Reply-To: <20090608143857.GG15070@csn.ul.ie>
On Mon, 8 Jun 2009, Mel Gorman wrote:
> > The tmpfs pages are unreclaimable and therefore should not be on the anon
> > lru.
> >
>
> tmpfs pages can be swap-backed so can be reclaimable. Regardless of what
> list they are on, we still need to know how many of them there are if
> this patch is to be avoided.
If they are reclaimable then why does it matter? They can be pushed out if
you configure zone reclaim to be that aggressive.
next prev parent reply other threads:[~2009-06-08 14:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 13:01 [PATCH 0/3] [RFC] Functional fix to zone_reclaim() and bring behaviour more in line with expectations Mel Gorman
2009-06-08 13:01 ` [PATCH 1/3] Reintroduce zone_reclaim_interval for when zone_reclaim() scans and fails to avoid CPU spinning at 100% on NUMA Mel Gorman
2009-06-08 13:31 ` Rik van Riel
2009-06-08 13:54 ` Mel Gorman
2009-06-08 14:33 ` Christoph Lameter
2009-06-08 14:38 ` Mel Gorman
2009-06-08 14:55 ` Christoph Lameter [this message]
2009-06-08 15:11 ` Mel Gorman
2009-06-10 5:23 ` Andrew Morton
2009-06-10 6:44 ` KOSAKI Motohiro
2009-06-10 10:00 ` Mel Gorman
2009-06-08 14:48 ` Rik van Riel
2009-06-09 8:08 ` Mel Gorman
2009-06-09 1:58 ` Wu Fengguang
2009-06-09 8:14 ` Mel Gorman
2009-06-09 8:25 ` Wu Fengguang
2009-06-09 8:31 ` Mel Gorman
2009-06-09 9:07 ` Wu Fengguang
2009-06-09 9:40 ` Mel Gorman
2009-06-09 13:38 ` Wu Fengguang
2009-06-09 15:06 ` Mel Gorman
2009-06-10 2:14 ` Wu Fengguang
2009-06-10 9:54 ` Mel Gorman
2009-06-09 7:48 ` KOSAKI Motohiro
2009-06-09 8:18 ` Mel Gorman
2009-06-09 8:45 ` KOSAKI Motohiro
2009-06-09 9:42 ` Mel Gorman
2009-06-09 9:45 ` KOSAKI Motohiro
2009-06-09 9:59 ` KOSAKI Motohiro
2009-06-09 10:44 ` Mel Gorman
2009-06-09 10:50 ` KOSAKI Motohiro
2009-06-08 13:01 ` [PATCH 2/3] Properly account for the number of page cache pages zone_reclaim() can reclaim Mel Gorman
2009-06-08 14:25 ` Christoph Lameter
2009-06-08 14:36 ` Mel Gorman
2009-06-09 2:25 ` Wu Fengguang
2009-06-09 8:27 ` Mel Gorman
2009-06-09 8:45 ` Wu Fengguang
2009-06-09 10:48 ` Mel Gorman
2009-06-09 12:08 ` Wu Fengguang
2009-06-09 8:55 ` KOSAKI Motohiro
2009-06-09 2:37 ` Wu Fengguang
2009-06-09 8:19 ` KOSAKI Motohiro
2009-06-09 8:47 ` Mel Gorman
2009-06-08 13:01 ` [PATCH 3/3] Do not unconditionally treat zones that fail zone_reclaim() as full Mel Gorman
2009-06-08 14:32 ` Christoph Lameter
2009-06-08 14:43 ` Mel Gorman
2009-06-09 3:11 ` Wu Fengguang
2009-06-09 8:50 ` Mel Gorman
2009-06-09 7:48 ` KOSAKI Motohiro
2009-06-09 9:25 ` Mel Gorman
2009-06-09 12:05 ` KOSAKI Motohiro
2009-06-09 13:28 ` Mel Gorman
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.1.10.0906081055170.21954@gentwo.org \
--to=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxram@us.ibm.com \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=yanmin.zhang@intel.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
all inboxes | Powered by JetHome®