From: Joel Schopp <jschopp@austin.ibm.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Patch] New zone ZONE_EASY_RECLAIM take 4. (Change PageHighMem())[8/8]
Date: Tue, 03 Jan 2006 15:40:57 -0600 [thread overview]
Message-ID: <43BAEF69.3020006@austin.ibm.com> (raw)
In-Reply-To: <20051220173217.1B18.Y-GOTO@jp.fujitsu.com>
> This patch is change PageHighMem()'s definition for i386.
> Easy reclaim zone is treated like highmem on i386.
This doesn't look like an i386 file, it looks like you are changing it
for all architectures that have HIGHMEM (do any other archs use
highmeme?). This may be fine, just wanted you to be aware.
>
> This is new patch at take 4.
>
> Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com>
>
> Index: zone_reclaim/include/linux/page-flags.h
> ===================================================================
> --- zone_reclaim.orig/include/linux/page-flags.h 2005-12-15 21:01:09.000000000 +0900
> +++ zone_reclaim/include/linux/page-flags.h 2005-12-15 21:24:07.000000000 +0900
> @@ -265,7 +265,7 @@ extern void __mod_page_state_offset(unsi
> #define TestSetPageSlab(page) test_and_set_bit(PG_slab, &(page)->flags)
>
> #ifdef CONFIG_HIGHMEM
> -#define PageHighMem(page) is_highmem(page_zone(page))
> +#define PageHighMem(page) is_higher_zone(page_zone(page))
> #else
> #define PageHighMem(page) 0 /* needed to optimize away at compile time */
> #endif
>
--
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:[~2006-01-03 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 8:53 Yasunori Goto
2006-01-03 21:40 ` Joel Schopp [this message]
2006-01-05 5:54 ` Yasunori Goto
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=43BAEF69.3020006@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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