From: David Rientjes <rientjes@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, mel@skynet.ie, clameter@engr.sgi.com,
akpm@linux-foundation.org
Subject: Re: [RFC} memory unplug patchset prep [8/16] counter for ZONE_MOVABLE
Date: Tue, 6 Mar 2007 08:11:22 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0703060029510.21900@chino.kir.corp.google.com> (raw)
In-Reply-To: <20070306135058.5ce2ab9d.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 6 Mar 2007, KAMEZAWA Hiroyuki wrote:
> Index: devel-tree-2.6.20-mm2/mm/page_alloc.c
> ===================================================================
> --- devel-tree-2.6.20-mm2.orig/mm/page_alloc.c
> +++ devel-tree-2.6.20-mm2/mm/page_alloc.c
> @@ -58,6 +58,7 @@ unsigned long totalram_pages __read_most
> unsigned long totalreserve_pages __read_mostly;
> long nr_swap_pages;
> int percpu_pagelist_fraction;
> +unsigned long total_movable_pages __read_mostly;
>
> static void __free_pages_ok(struct page *page, unsigned int order);
>
> @@ -1571,6 +1572,20 @@ static unsigned int nr_free_zone_pages(i
> return sum;
> }
>
> +unsigned int nr_free_movable_pages(void)
> +{
> + unsigned long nr_pages = 0;
> + struct zone *zone;
> + int nid;
> + if (is_configured_zone(ZONE_MOVABLE)) {
> + /* we want to count *only* pages in movable zone */
> + for_each_online_node(nid) {
> + zone = &(NODE_DATA(nid)->node_zones[ZONE_MOVABLE]);
> + nr_pages += zone_page_state(zone, NR_FREE_PAGES);
> + }
> + }
> + return nr_pages;
> +}
> /*
> * Amount of free RAM allocatable within ZONE_DMA and ZONE_NORMAL
> */
On each online node, zone should be
zone = NODE_DATA(nid)->node_sizes + ZONE_MOVABLE;
Also, you should probably only declare this function on #ifdef
CONFIG_ZONE_MOVABLE and #define it to "do {} while(0)" otherwise.
> @@ -1584,7 +1599,7 @@ unsigned int nr_free_buffer_pages(void)
> */
> unsigned int nr_free_pagecache_pages(void)
> {
> - return nr_free_zone_pages(gfp_zone(GFP_HIGHUSER));
> + return nr_free_zone_pages(gfp_zone(GFP_HIGH_MOVABLE));
> }
>
> /*
> @@ -1633,6 +1648,8 @@ void si_meminfo(struct sysinfo *val)
> val->totalhigh = totalhigh_pages;
> val->freehigh = nr_free_highpages();
> val->mem_unit = PAGE_SIZE;
> + val->movable = total_movable_pages;
> + val->free_movable = nr_free_movable_pages();
> }
>
> EXPORT_SYMBOL(si_meminfo);
> @@ -1654,6 +1671,13 @@ void si_meminfo_node(struct sysinfo *val
> val->totalhigh = 0;
> val->freehigh = 0;
> }
> + if (is_configured_zone(ZONE_MOVABLE)) {
> + val->movable +=
> + pgdat->node_zones[ZONE_MOVABLE].present_pages;
> + val->free_movable +=
> + zone_page_state(&pgdat->node_zones[ZONE_MOVABLE],
> + NR_FREE_PAGES);
> + }
> val->mem_unit = PAGE_SIZE;
> }
> #endif
Don't you want assignments here instead of accumulations? val->movable
and val->free_movable probably shouldn't be the only members in
si_meminfo_node() that accumulate.
Your first patch in this patchset actually sets val->totalhigh and
val->freehigh both to 0 in the !is_configured_zone(ZONE_HIGHMEM) case. Do
these need the same assignments for movable and free_movable in the
!is_configured_zone(ZONE_MOVABLE) case?
> Index: devel-tree-2.6.20-mm2/include/linux/kernel.h
> ===================================================================
> --- devel-tree-2.6.20-mm2.orig/include/linux/kernel.h
> +++ devel-tree-2.6.20-mm2/include/linux/kernel.h
> @@ -329,6 +329,8 @@ struct sysinfo {
> unsigned short pad; /* explicit padding for m68k */
> unsigned long totalhigh; /* Total high memory size */
> unsigned long freehigh; /* Available high memory size */
> + unsigned long movable; /* pages used only for data */
> + unsigned long free_movable; /* Avaiable pages in movable */
> unsigned int mem_unit; /* Memory unit size in bytes */
> char _f[20-2*sizeof(long)-sizeof(int)]; /* Padding: libc5 uses this.. */
> };
Please add #ifdef's to CONFIG_ZONE_MOVABLE around these members in struct
sysinfo so we incur no penalty if we choose not to enable this option.
> Index: devel-tree-2.6.20-mm2/mm/vmstat.c
> ===================================================================
> --- devel-tree-2.6.20-mm2.orig/mm/vmstat.c
> +++ devel-tree-2.6.20-mm2/mm/vmstat.c
> @@ -426,8 +426,14 @@ const struct seq_operations fragmentatio
> #define TEXT_FOR_HIGHMEM(xx)
> #endif
>
> +#ifdef CONFIG_ZONE_MOVABLE
> +#define TEXT_FOR_MOVABLE(xx) xx "_movable",
> +#else
> +#define TXT_FOR_MOVABLE(xx)
> +#endif
> +
> #define TEXTS_FOR_ZONES(xx) TEXT_FOR_DMA(xx) TEXT_FOR_DMA32(xx) xx "_normal", \
> - TEXT_FOR_HIGHMEM(xx)
> + TEXT_FOR_HIGHMEM(xx) TEXT_FOR_MOVABLE(xx)
>
> static const char * const vmstat_text[] = {
> /* Zoned VM counters */
>
This broke my build because TEXT_FOR_MOVABLE() is misspelled on
!CONFIG_ZONE_MOVABLE.
David
--
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-03-06 16:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 4:32 [RFC} memory unplug patchset prep [0/16] KAMEZAWA Hiroyuki
2007-03-06 4:42 ` [RFC} memory unplug patchset prep [1/16] zone ids cleanup KAMEZAWA Hiroyuki
2007-03-06 15:36 ` David Rientjes
2007-03-07 1:21 ` KAMEZAWA Hiroyuki
2007-03-06 4:43 ` [RFC} memory unplug patchset prep [2/16] gathering alloc_zeroed_user_highpage() KAMEZAWA Hiroyuki
2007-03-06 15:54 ` David Rientjes
2007-03-07 1:46 ` KAMEZAWA Hiroyuki
2007-03-06 4:44 ` [RFC} memory unplug patchset prep [3/16] define is_identity_mapped KAMEZAWA Hiroyuki
2007-03-06 15:55 ` David Rientjes
2007-03-07 1:48 ` KAMEZAWA Hiroyuki
2007-03-06 4:45 ` [RFC} memory unplug patchset prep [4/16] ZONE_MOVABLE KAMEZAWA Hiroyuki
2007-03-06 16:06 ` David Rientjes
2007-03-07 1:51 ` KAMEZAWA Hiroyuki
2007-03-06 4:47 ` [RFC} memory unplug patchset prep [5/16] GFP_MOVABLE KAMEZAWA Hiroyuki
2007-03-06 4:48 ` [RFC} memory unplug patchset prep [6/16] alloc_zeroed_user_high_movable KAMEZAWA Hiroyuki
2007-03-06 4:49 ` [RFC} memory unplug patchset prep [7/16] change caller's gfp_mask KAMEZAWA Hiroyuki
2007-03-06 4:50 ` [RFC} memory unplug patchset prep [8/16] counter for ZONE_MOVABLE KAMEZAWA Hiroyuki
2007-03-06 16:11 ` David Rientjes [this message]
2007-03-07 1:55 ` KAMEZAWA Hiroyuki
2007-03-06 4:52 ` [RFC} memory unplug patchset prep [9/16] create movable zone at boot KAMEZAWA Hiroyuki
2007-03-06 16:06 ` David Rientjes
2007-03-07 2:02 ` KAMEZAWA Hiroyuki
2007-03-06 4:53 ` [RFC} memory unplug patchset prep [10/16] ia64 support KAMEZAWA Hiroyuki
2007-03-06 4:55 ` [RFC} memory unplug patchset prep [11/16] page isolation core KAMEZAWA Hiroyuki
2007-03-06 4:56 ` [RFC} memory unplug patchset prep [12/16] drain all pages KAMEZAWA Hiroyuki
2007-03-06 4:57 ` [RFC} memory unplug patchset prep [13/16] isolate freed pages KAMEZAWA Hiroyuki
2007-03-06 4:59 ` [RFC} memory unplug patchset prep [14/16] memory unplug core KAMEZAWA Hiroyuki
2007-03-06 5:00 ` [RFC} memory unplug patchset prep [15/16] hot-unplug interface for ia64 KAMEZAWA Hiroyuki
2007-03-06 5:02 ` [RFC} memory unplug patchset prep [16/16] migration nocontext KAMEZAWA Hiroyuki
2007-03-06 15:24 ` [RFC} memory unplug patchset prep [0/16] David Rientjes
2007-03-07 2:24 ` KAMEZAWA Hiroyuki
2007-03-07 2:31 ` David Rientjes
2007-03-07 2:44 ` KAMEZAWA Hiroyuki
2007-03-07 19:44 ` Mark Gross
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=Pine.LNX.4.64.0703060029510.21900@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@engr.sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@skynet.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