From: Andy Whitcroft <apw@shadowen.org>
To: Mel Gorman <mel@csn.ul.ie>, Bob Picco <bob.picco@hp.com>
Cc: Andy Whitcroft <apw@shadowen.org>,
Dave Hansen <hansendc@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] lumpy: move to using pfn_valid_within()
Date: Wed, 21 Mar 2007 19:16:27 +0000 [thread overview]
Message-ID: <98524116072c1d68263889385212f639@pinky> (raw)
In-Reply-To: <exportbomb.1174504472@pinky>
Switch to using pfn_valid_within() in lumpy reclaim.
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
Acked-by: Mel Gorman <mel@csn.ul.ie>
---
diff --git a/mm/vmscan.c b/mm/vmscan.c
index c3dc544..cf55c57 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -722,11 +722,10 @@ static unsigned long isolate_lru_pages(unsigned long nr_to_scan,
/* The target page is in the block, ignore it. */
if (unlikely(pfn == page_pfn))
continue;
-#ifdef CONFIG_HOLES_IN_ZONE
+
/* Avoid holes within the zone. */
- if (unlikely(!pfn_valid(pfn)))
+ if (unlikely(!pfn_valid_within(pfn)))
break;
-#endif
cursor_page = pfn_to_page(pfn);
/* Check that we have not crossed a zone boundary. */
next prev parent reply other threads:[~2007-03-21 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703211510340.15309@skynet.skynet.ie>
2007-03-21 19:14 ` [PATCH 0/3] pfn_valid_within() HOLES_WITHIN_ZONES helper Andy Whitcroft
2007-03-21 19:15 ` [PATCH 1/3] add pfn_valid_within helper for sub-MAX_ORDER hole detection Andy Whitcroft
2007-03-21 23:23 ` Nick Piggin
2007-03-21 23:46 ` Andrew Morton
2007-03-21 19:15 ` [PATCH 2/3] anti-fragmentation: switch over to pfn_valid_within() Andy Whitcroft
2007-03-21 19:16 ` Andy Whitcroft [this message]
2007-03-21 20:55 ` [PATCH 0/3] pfn_valid_within() HOLES_WITHIN_ZONES helper Bob Picco
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=98524116072c1d68263889385212f639@pinky \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=hansendc@us.ibm.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®