linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Subject: Re: [patch] mm: suppress pfn range output for zones without pages
Date: Thu, 11 Feb 2010 12:25:08 +0000	[thread overview]
Message-ID: <20100211122507.GA32292@csn.ul.ie> (raw)
In-Reply-To: <alpine.DEB.2.00.1002110129280.3069@chino.kir.corp.google.com>

On Thu, Feb 11, 2010 at 01:29:58AM -0800, David Rientjes wrote:
> free_area_init_nodes() emits pfn ranges for all zones on the system.
> There may be no pages on a higher zone, however, due to memory
> limitations or the use of the mem= kernel parameter.  For example:
> 
> Zone PFN ranges:
>   DMA      0x00000001 -> 0x00001000
>   DMA32    0x00001000 -> 0x00100000
>   Normal   0x00100000 -> 0x00100000
> 
> The implementation copies the previous zone's highest pfn, if any, as the
> next zone's lowest pfn.  If its highest pfn is then greater than the
> amount of addressable memory, the upper memory limit is used instead.
> Thus, both the lowest and highest possible pfn for higher zones without
> memory may be the same.
> 
> The output is now suppressed for zones that do not have a valid pfn
> range.
> 

I see no problem with the patch. Was it a major problem or just
confusing?

> Cc: Mel Gorman <mel@csn.ul.ie>
> Signed-off-by: David Rientjes <rientjes@google.com>

Reviewed-by: Mel Gorman <mel@csn.ul.ie>

> ---
>  mm/page_alloc.c       |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4377,6 +4377,9 @@ void __init free_area_init_nodes(unsigned long *max_zone_pfn)
>  	for (i = 0; i < MAX_NR_ZONES; i++) {
>  		if (i == ZONE_MOVABLE)
>  			continue;
> +		if (arch_zone_lowest_possible_pfn[i] ==
> +		    arch_zone_highest_possible_pfn[i])
> +			continue;
>  		printk("  %-8s %0#10lx -> %0#10lx\n",
>  				zone_names[i],
>  				arch_zone_lowest_possible_pfn[i],
> 

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
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>

  reply	other threads:[~2010-02-11 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  9:29 [patch] mm: suppress pfn range output for zones without pages David Rientjes
2010-02-11 12:25 ` Mel Gorman [this message]
2010-02-11 21:26   ` David Rientjes
2010-02-11 22:27     ` Andrew Morton
2010-02-11 20:07 ` Christoph Lameter
2010-02-11 22:13   ` David Rientjes
2010-02-11 22:32     ` Christoph Lameter
2010-02-11 23:02       ` [patch v2] " David Rientjes
2010-02-12 15:44         ` Christoph Lameter
2010-02-11 22:33     ` [patch] " Andrew Morton

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=20100211122507.GA32292@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).