linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mel Gorman <mel@csn.ul.ie>
Cc: yhlu.kernel@gmail.com, linux-mm@kvack.org
Subject: Re: + mm-remove-find_max_pfn_with_active_regions.patch added to -mm tree
Date: Mon, 28 Jul 2008 13:55:21 -0700	[thread overview]
Message-ID: <20080728135521.12b1b041.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080728203959.GA29548@csn.ul.ie>

On Mon, 28 Jul 2008 21:40:00 +0100
Mel Gorman <mel@csn.ul.ie> wrote:

> > how about KERN_DEBUG?
> > 
> > please check
> > 
> 
> Still NAK due to the noise.

blah.  I changed the patch to this:

--- a/include/linux/mm.h~mm-remove-find_max_pfn_with_active_regions
+++ a/include/linux/mm.h
@@ -1041,7 +1041,6 @@ extern unsigned long absent_pages_in_ran
 extern void get_pfn_range_for_nid(unsigned int nid,
 			unsigned long *start_pfn, unsigned long *end_pfn);
 extern unsigned long find_min_pfn_with_active_regions(void);
-extern unsigned long find_max_pfn_with_active_regions(void);
 extern void free_bootmem_with_active_regions(int nid,
 						unsigned long max_low_pfn);
 typedef int (*work_fn_t)(unsigned long, unsigned long, void *);
diff -puN mm/page_alloc.c~mm-remove-find_max_pfn_with_active_regions mm/page_alloc.c
--- a/mm/page_alloc.c~mm-remove-find_max_pfn_with_active_regions
+++ a/mm/page_alloc.c
@@ -3753,23 +3753,6 @@ unsigned long __init find_min_pfn_with_a
 	return find_min_pfn_for_node(MAX_NUMNODES);
 }
 
-/**
- * find_max_pfn_with_active_regions - Find the maximum PFN registered
- *
- * It returns the maximum PFN based on information provided via
- * add_active_range().
- */
-unsigned long __init find_max_pfn_with_active_regions(void)
-{
-	int i;
-	unsigned long max_pfn = 0;
-
-	for (i = 0; i < nr_nodemap_entries; i++)
-		max_pfn = max(max_pfn, early_node_map[i].end_pfn);
-
-	return max_pfn;
-}
-
 /*
  * early_calculate_totalpages()
  * Sum pages in active regions for movable zone.
_


Which is what it should always have been.  Only do one thing per patch,
please.  The presence of the work "also" in the changelog is usually a
big hint that it should be split up.


--
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:[~2008-07-28 20:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200807280313.m6S3DHDk017400@imap1.linux-foundation.org>
2008-07-28  9:16 ` Mel Gorman
2008-07-28 11:15   ` Yinghai Lu
2008-07-28 11:38     ` Mel Gorman
2008-07-28 18:25       ` Yinghai Lu
2008-07-28 19:15         ` Mel Gorman
2008-07-28 19:38           ` Yinghai Lu
2008-07-28 20:00             ` Mel Gorman
2008-07-28 20:14               ` Yinghai Lu
2008-07-28 20:40                 ` Mel Gorman
2008-07-28 20:55                   ` Andrew Morton [this message]
2008-07-28 21:16                     ` Mel Gorman
2008-07-28 21:24                   ` Yinghai Lu

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=20080728135521.12b1b041.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=yhlu.kernel@gmail.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