[lkml]   [2012]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 046/181] mm: remove sparsemem allocation details from the bootmem allocator
On Sat, Jun 23, 2012 at 3:06 PM, Johannes Weiner <> wrote:
> On Sat, Jun 23, 2012 at 11:58:02AM -0700, Yinghai Lu wrote:
>> +again:
>> +     p = ___alloc_bootmem_node_nopanic(NODE_DATA(nid), size,
>> +                                       SMP_CACHE_BYTES, goal, limit);
>> +     if (!p && limit) {
>> +             limit = 0;
>> +             goto again;
>> +     }
> I was aware that __alloc_bootmem_node_nopanic does a slightly
> different fallback sequence, but as soon as you go outside the
> section, you have a node-section-dependency either way.

you need to make sure, first try to get the in the same section, then same node.

> Without this patch, it would retry without the node first, then
> without the goal.  With your patch, you would try to limit the upper
> end, but you may already go below the requested section.  What would
> the limit gain?

goal: start of section
limit: start of next section.

the layout should be

before your commit:
1. first try: start_of_range_same_section....end_of_range_same_section
2. second try: on same node.

with your commit:
1. first try: start_of_range_same_section....end_of_range_same_node.
===> it would get buffer out of same section.
2. second try: 0...0, aka 0... -1UL

with this patch:
1. first try: start_of_range_same_section....end_of_range_same_section
2. second try: 0...end_of_range_of_same_section.
3. third try: start_of_range_same_section...0, aka
4. third try: 0...0, aka 0...-1UL;

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2012-06-24 01:01    [W:0.071 / U:29.620 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site