Messages in this thread | | | Date | Tue, 17 Apr 2012 20:30:42 +0200 | From | Sam Ravnborg <> | Subject | Re: Weirdness in __alloc_bootmem_node_high |
| |
On Tue, Apr 17, 2012 at 11:07:10AM -0700, Yinghai Lu wrote: > On Tue, Apr 17, 2012 at 10:32 AM, Michal Hocko <mhocko@suse.cz> wrote: > > On Tue 17-04-12 10:12:30, Yinghai Lu wrote: > >> > >> We are not using bootmem with x86 now, so could remove those workaround now. > > > > Could you be more specific about what the workaround is used for? > > Don't bootmem allocating too low to use up all low memory. like for > system with lots of memory for sparse vmemmap. > > when nobootmem.c is used, __alloc_bootmem_node_high is the same as > __alloc_bootmem_node.
It would be nice if someone familiar with the memblock/bootmem internals could cleans up the leftovers from the migration of x86 to memblock / nobootmem.
This would be less to be confused about when other migrate to use memblock.
Sam
| |