lkml.org 
[lkml]   [2012]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Weirdness in __alloc_bootmem_node_high
    On Fri 20-04-12 12:32:38, Yinghai Lu wrote:
    > On Fri, Apr 20, 2012 at 12:29 PM, Michal Hocko <mhocko@suse.cz> wrote:
    > > This is what I can see in the current (Linus) git:
    > > ./arch/sparc/Kconfig:   select SPARSEMEM_VMEMMAP_ENABLE
    > > ./arch/powerpc/Kconfig: select SPARSEMEM_VMEMMAP_ENABLE
    > > ./arch/ia64/Kconfig:    select SPARSEMEM_VMEMMAP_ENABLE
    > > ./arch/s390/Kconfig:    select SPARSEMEM_VMEMMAP_ENABLE
    > > ./arch/s390/Kconfig:    select SPARSEMEM_VMEMMAP
    > > ./arch/x86/Kconfig:     select SPARSEMEM_VMEMMAP_ENABLE if X86_64
    > >
    > > So there are more arches which enable SPARSEMEM_VMEMMAP so the function
    > > is used. Or am I missing something?
    >
    > MAX_DMA32_PFN is not defined for them.

    Ahh, you are right except that it is defined for x86 but that one uses
    nobootmem. I missed that point.

    Thanks
    --
    Michal Hocko
    SUSE Labs
    SUSE LINUX s.r.o.
    Lihovarska 1060/12
    190 00 Praha 9
    Czech Republic
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2012-04-20 21:43    [W:0.030 / U:60.648 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site