linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@suse.cz>,
	Gavin Shan <shangw@linux.vnet.ibm.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm, sparse: allocate bootmem without panicing in sparse_mem_maps_populate_node
Date: Thu, 27 Dec 2012 17:41:28 -0500	[thread overview]
Message-ID: <50DCCE98.70000@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212271422280.18214@chino.kir.corp.google.com>

On 12/27/2012 05:23 PM, David Rientjes wrote:
> On Sun, 23 Dec 2012, Sasha Levin wrote:
> 
>> diff --git a/mm/sparse.c b/mm/sparse.c
>> index 6b5fb76..72a0db6 100644
>> --- a/mm/sparse.c
>> +++ b/mm/sparse.c
>> @@ -401,7 +401,7 @@ void __init sparse_mem_maps_populate_node(struct page **map_map,
>>  	}
>>  
>>  	size = PAGE_ALIGN(size);
>> -	map = __alloc_bootmem_node_high(NODE_DATA(nodeid), size * map_count,
>> +	map = __alloc_bootmem_node_high_nopanic(NODE_DATA(nodeid), size * map_count,
>>  					 PAGE_SIZE, __pa(MAX_DMA_ADDRESS));
>>  	if (map) {
>>  		for (pnum = pnum_begin; pnum < pnum_end; pnum++) {
> 
> What tree is this series based on?  There's no 
> __alloc_bootmem_node_high_nopanic() either in 3.8-rc1 nor in linux-next.
> 

This is me getting git-send-email wrong and forgetting the first patch that adds it.

Sorry, will resend.


Thanks,
Sasha

--
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:[~2012-12-27 22:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-23 20:15 [PATCH 1/3] mm, sparse: allocate bootmem without panicing in sparse_mem_maps_populate_node Sasha Levin
2012-12-23 20:15 ` [PATCH 2/3] mm, bootmem: panic in bootmem alloc functions even if slab is available Sasha Levin
2012-12-27 22:25   ` David Rientjes
2012-12-27 22:27     ` Pekka Enberg
2012-12-27 22:31       ` David Rientjes
2012-12-27 22:38         ` Pekka Enberg
2012-12-27 22:40     ` Sasha Levin
2012-12-27 23:04       ` David Rientjes
2012-12-27 23:07         ` Sasha Levin
2012-12-28 14:42           ` JoonSoo Kim
2012-12-28 19:16             ` Yinghai Lu
2012-12-23 20:15 ` [PATCH 3/3] mm, sparse: don't check return value of alloc_bootmem calls Sasha Levin
2012-12-27 22:28   ` David Rientjes
2012-12-27 22:23 ` [PATCH 1/3] mm, sparse: allocate bootmem without panicing in sparse_mem_maps_populate_node David Rientjes
2012-12-27 22:41   ` Sasha Levin [this message]

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=50DCCE98.70000@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).