linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, rientjes@google.com, hannes@cmpxchg.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH 1/5] mm/sparse: check size of struct mm_section
Date: Mon, 25 Jun 2012 18:03:22 +0200	[thread overview]
Message-ID: <20120625160322.GE19810@tiehlicka.suse.cz> (raw)
In-Reply-To: <1340466776-4976-1-git-send-email-shangw@linux.vnet.ibm.com>

On Sat 23-06-12 23:52:52, Gavin Shan wrote:
> Platforms like PPC might need two level mem_section for SPARSEMEM
> with enabled CONFIG_SPARSEMEM_EXTREME. On the other hand, the
> memory section descriptor might be allocated from bootmem allocator
> with PAGE_SIZE alignment. In order to fully utilize the memory chunk
> allocated from bootmem allocator, it'd better to assure memory
> sector descriptor won't run across the boundary (PAGE_SIZE).

Why? The memory is continuous, right?

> 
> The patch introduces the check on size of "struct mm_section" to
> assure that.
> 
> Signed-off-by: Gavin Shan <shangw@linux.vnet.ibm.com>
> ---
>  mm/sparse.c |    9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/mm/sparse.c b/mm/sparse.c
> index 6a4bf91..afd0998 100644
> --- a/mm/sparse.c
> +++ b/mm/sparse.c
> @@ -63,6 +63,15 @@ static struct mem_section noinline __init_refok *sparse_index_alloc(int nid)
>  	unsigned long array_size = SECTIONS_PER_ROOT *
>  				   sizeof(struct mem_section);
>  
> +	/*
> +	 * The root memory section descriptor might be allocated
> +	 * from bootmem, which has minimal memory chunk requirement
> +	 * of page. In order to fully utilize the memory, the sparse
> +	 * memory section descriptor shouldn't run across the boundary
> +	 * that bootmem allocator has.
> +	 */
> +	BUILD_BUG_ON(PAGE_SIZE % sizeof(struct mem_section));
> +
>  	if (slab_is_available()) {
>  		if (node_state(nid, N_HIGH_MEMORY))
>  			section = kmalloc_node(array_size, GFP_KERNEL, nid);
> -- 
> 1.7.9.5
> 
> --
> 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>

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

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

  parent reply	other threads:[~2012-06-25 16:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 15:52 Gavin Shan
2012-06-23 15:52 ` [PATCH 2/5] mm/sparse: optimize sparse_index_alloc Gavin Shan
2012-06-25 15:30   ` Michal Hocko
2012-06-26  6:07     ` Gavin Shan
2012-06-26  7:04       ` Michal Hocko
2012-06-26  7:13         ` Gavin Shan
2012-06-23 15:52 ` [PATCH 3/5] mm/sparse: fix possible memory leak Gavin Shan
2012-06-25 15:48   ` Michal Hocko
2012-06-26  6:11     ` Gavin Shan
2012-06-26  7:14       ` Michal Hocko
2012-06-26  7:17         ` Gavin Shan
2012-06-23 15:52 ` [PATCH 4/5] mm/sparse: more check on mem_section number Gavin Shan
2012-06-26 16:15   ` Dave Hansen
2012-06-27  0:29     ` Gavin Shan
2012-06-23 15:52 ` [PATCH 5/5] mm/sparse: return 0 if root mem_section exists Gavin Shan
2012-06-24 19:18   ` KOSAKI Motohiro
2012-06-25  1:09     ` Gavin Shan
2012-06-25 15:39   ` Michal Hocko
2012-06-25 16:03 ` Michal Hocko [this message]
2012-06-25 16:35   ` [PATCH 1/5] mm/sparse: check size of struct mm_section Gavin Shan
2012-06-26  7:39     ` Michal Hocko
2012-06-26  7:48       ` Gavin Shan
2012-06-26  8:06         ` Michal Hocko
2012-06-26  8:24           ` Gavin Shan
2012-06-26 17:57             ` Michal Hocko
2012-06-27  3:01               ` Gavin Shan

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=20120625160322.GE19810@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    --cc=shangw@linux.vnet.ibm.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