[PATCH v3 03/20] mm, hugetlb: fix subpool accounting handling

2013-09-05 Thread Joonsoo Kim
There is a case that we attempt to allocate a hugepage with chg = 0 and avoid_reserve = 1. Although chg = 0 means that it has a reserved hugepage, we wouldn't use it, since avoid_reserve = 1 represents that we don't want to allocate a hugepage from a reserved pool. This happens when the parent

[PATCH v3 03/20] mm, hugetlb: fix subpool accounting handling

2013-09-05 Thread Joonsoo Kim
There is a case that we attempt to allocate a hugepage with chg = 0 and avoid_reserve = 1. Although chg = 0 means that it has a reserved hugepage, we wouldn't use it, since avoid_reserve = 1 represents that we don't want to allocate a hugepage from a reserved pool. This happens when the parent

[PATCH v3 03/20] mm, hugetlb: fix subpool accounting handling

2013-09-05 Thread Joonsoo Kim
There is a case that we attempt to allocate a hugepage with chg = 0 and avoid_reserve = 1. Although chg = 0 means that it has a reserved hugepage, we wouldn't use it, since avoid_reserve = 1 represents that we don't want to allocate a hugepage from a reserved pool. This happens when the parent

[PATCH v3 03/20] mm, hugetlb: fix subpool accounting handling

2013-09-05 Thread Joonsoo Kim
There is a case that we attempt to allocate a hugepage with chg = 0 and avoid_reserve = 1. Although chg = 0 means that it has a reserved hugepage, we wouldn't use it, since avoid_reserve = 1 represents that we don't want to allocate a hugepage from a reserved pool. This happens when the parent