mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Christoph Lameter <clameter@sgi.com>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH] mm: allocate section_map for sparse_init
Date: Thu, 13 Mar 2008 11:19:35 +0000	[thread overview]
Message-ID: <20080313111934.GA12351@csn.ul.ie> (raw)
In-Reply-To: <86802c440803121051q20023badsf8e6e0571f4bb92e@mail.gmail.com>

On (12/03/08 10:51), Yinghai Lu didst pronounce:
> [PATCH] mm: allocate section_map for sparse_init
> 
> allocate section_map in bootmem instead of using __initdata.
> 
> need to apply it after
>         [PATCH] mm: fix boundary checking in free_bootmem_core
>         [PATCH] mm: make mem_map allocation continuous.
> 
> 
> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>

> Index: linux-2.6/mm/sparse.c
> ===================================================================
> --- linux-2.6.orig/mm/sparse.c
> +++ linux-2.6/mm/sparse.c
> @@ -285,8 +285,6 @@ struct page __init *sparse_early_mem_map
>  	return NULL;
>  }
>  
> -/* section_map pointer array is 64k */
> -static __initdata struct page *section_map[NR_MEM_SECTIONS];
>  /*
>   * Allocate the accumulated non-linear sections, allocate a mem_map
>   * for each and record the physical to section mapping.
> @@ -296,6 +294,9 @@ void __init sparse_init(void)
>  	unsigned long pnum;
>  	struct page *map;
>  	unsigned long *usemap;
> +	struct page **section_map;
> +	int size;
> +	int node;
>  
>  	/*
>  	 * map is using big page (aka 2M in x86 64 bit)
> @@ -305,13 +306,17 @@ void __init sparse_init(void)
>  	 * then in big system, the memmory will have a lot hole...
>  	 * here try to allocate 2M pages continously.
>  	 */
> +	size = sizeof(struct page *) * NR_MEM_SECTIONS;
> +	section_map = alloc_bootmem(size);
> +	if (!section_map)
> +		panic("can not allocate section_map\n");
> +
>  	for (pnum = 0; pnum < NR_MEM_SECTIONS; pnum++) {
>  		if (!present_section_nr(pnum))
>  			continue;
>  		section_map[pnum] = sparse_early_mem_map_alloc(pnum);
>  	}
>  
> -
>  	for (pnum = 0; pnum < NR_MEM_SECTIONS; pnum++) {
>  		if (!present_section_nr(pnum))
>  			continue;
> @@ -327,6 +332,9 @@ void __init sparse_init(void)
>  		sparse_init_one_section(__nr_to_section(pnum), pnum, map,
>  								usemap);
>  	}
> +
> +	for_each_online_node(node)
> +		free_bootmem_node(NODE_DATA(node), __pa(section_map), size);

Why are you iterating every online node here instead of just calling
free_bootmem(__pa(section_map), size) ?

>  }
>  
>  #ifdef CONFIG_MEMORY_HOTPLUG


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

  reply	other threads:[~2008-03-13 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 17:51 Yinghai Lu
2008-03-13 11:19 ` Mel Gorman [this message]
2008-03-13 18:02   ` Yinghai Lu
2008-03-18  9:41     ` Mel Gorman
2008-03-18 17:57       ` 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=20080313111934.GA12351@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®