【OLK-5.10】回合两个hugetlb相关的bugfix

hugetlb: fix wrong use of nr_online_nodes

Certain systems are designed to have sparse/discontiguous nodes.  In this
    case, nr_online_nodes can not be used to walk through numa node.  Also, a
    valid node may be greater than nr_online_nodes.
    
    However, in hugetlb, it is assumed that nodes are contiguous.
    
    For sparse/discontiguous nodes, the current code may treat a valid node
    as invalid, and will fail to allocate all hugepages on a valid node that
    "nid >= nr_online_nodes".
    
    As David suggested:
    
            if (tmp >= nr_online_nodes)
                    goto invalid;
    
    Just imagine node 0 and node 2 are online, and node 1 is offline.
    Assuming that "node < 2" is valid is wrong.
    
    Recheck all the places that use nr_online_nodes, and repair them one by
    one.

hugetlb: fix hugepages_setup when deal with pernode

Hugepages can be specified to pernode since "hugetlbfs: extend the
    definition of hugepages parameter to support node allocation", but the
    following problem is observed.
    
    Confusing behavior is observed when both 1G and 2M hugepage is set
    after "numa=off".
     cmdline hugepage settings:
      hugepagesz=1G hugepages=0:3,1:3
      hugepagesz=2M hugepages=0:1024,1:1024
     results:
      HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
      HugeTLB registered 2.00 MiB page size, pre-allocated 1024 pages
    
    Furthermore, confusing behavior can be also observed when an invalid node
    behind a valid node.  To fix this, never allocate any typical hugepage
    when an invalid parameter is received.

GVP openEuler/kernel
Closed

Content Risk Flag

Comments (2)

GVPopenEuler/kernelClosed

Content Risk Flag