From: Andy Whitcroft <apw@shadowen.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: David Rientjes <rientjes@google.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, mel@csn.ul.ie, y-goto@jp.fujitsu.com,
hugh@veritas.com
Subject: Re: [RFC] memory unplug v5 [5/6] page unplug
Date: Fri, 15 Jun 2007 15:40:01 +0100 [thread overview]
Message-ID: <4672A4C1.1070909@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706150732510.7400@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Thu, 14 Jun 2007, David Rientjes wrote:
>
>>> + struct zone *zone = NULL;
>>> + struct page *page;
>>> + for (pfn = start_pfn;
>>> + pfn < end_pfn;
>>> + pfn += MAX_ORDER_NR_PAGES) {
>>> +#ifdef CONFIG_HOLES_IN_ZONE
>>> + int i;
>>> + for (i = 0; i < MAX_ORDER_NR_PAGES; i++) {
>>> + if (pfn_valid_within(pfn + i))
>>> + break;
>>> + }
>>> + if (i == MAX_ORDER_NR_PAGES)
>>> + continue;
>>> + page = pfn_to_page(pfn + i);
>>> +#else
>>> + page = pfn_to_page(pfn);
>>> +#endif
>> Please extract this out to inlined functions that are conditional are
>> CONFIG_HOLES_IN_ZONE.
>
> And we need to deal with HOLES_IN_ZONE because the sparsemem virtual
> memmap patchset was not merged and therefore we cannot get rid of
> VIRTUAL_MEM_MAP.
>
> Andy, any progress? Do you want me to do another patchset?
I believe I've got the latest. I'll sort out the feedback over the
weekend and get a new patchset out, to Andrew.
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-15 14:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 6:56 [RFC] memory unplug v5 [0/6] intro KAMEZAWA Hiroyuki
2007-06-14 6:59 ` [RFC] memory unplug v5 [1/6] migration by kernel KAMEZAWA Hiroyuki
2007-06-14 7:01 ` Christoph Lameter
2007-06-14 7:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:22 ` Christoph Lameter
2007-06-14 7:41 ` KAMEZAWA Hiroyuki
2007-06-14 7:47 ` Christoph Lameter
2007-06-14 8:29 ` KAMEZAWA Hiroyuki
2007-06-14 14:19 ` Christoph Lameter
2007-06-14 16:02 ` KAMEZAWA Hiroyuki
2007-06-14 16:12 ` Christoph Lameter
2007-06-14 16:15 ` KAMEZAWA Hiroyuki
2007-06-14 18:04 ` Mel Gorman
2007-06-14 22:31 ` KAMEZAWA Hiroyuki
2007-06-15 9:43 ` KAMEZAWA Hiroyuki
2007-06-15 9:53 ` KAMEZAWA Hiroyuki
2007-06-15 14:41 ` Christoph Lameter
2007-06-15 15:36 ` KAMEZAWA Hiroyuki
2007-06-14 7:00 ` [RFC] memory unplug v5 [2/6] isolate lru page race fix KAMEZAWA Hiroyuki
2007-06-14 7:01 ` [RFC] memory unplug v5 [3/6] walk memory resources assist function KAMEZAWA Hiroyuki
2007-06-15 6:05 ` David Rientjes
2007-06-15 6:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:03 ` [RFC] memory unplug v5 [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-15 15:46 ` Dave Hansen
2007-06-15 16:59 ` KAMEZAWA Hiroyuki
2007-06-14 7:04 ` [RFC] memory unplug v5 [5/6] page unplug KAMEZAWA Hiroyuki
2007-06-15 6:04 ` David Rientjes
2007-06-15 6:12 ` KAMEZAWA Hiroyuki
2007-06-15 14:35 ` Christoph Lameter
2007-06-15 14:40 ` Andy Whitcroft [this message]
2007-06-15 15:52 ` Dave Hansen
2007-06-15 17:03 ` KAMEZAWA Hiroyuki
2007-06-15 21:09 ` Dave Hansen
2007-06-14 7:06 ` [RFC] memory unplug v5 [6/6] ia64 interface KAMEZAWA Hiroyuki
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=4672A4C1.1070909@shadowen.org \
--to=apw@shadowen.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=rientjes@google.com \
--cc=y-goto@jp.fujitsu.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