Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-27 Thread Joonsoo Kim
> >> @@ -2504,6 +2498,8 @@ static int hugetlb_cow(struct mm_struct *mm, struct > >> vm_area_struct *vma, > >>struct hstate *h = hstate_vma(vma); > >>struct page *old_page, *new_page; > >>int outside_reserve = 0; > >> + long chg; > >> + bool use_reserve; > >>unsigned long

Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-27 Thread Joonsoo Kim
@@ -2504,6 +2498,8 @@ static int hugetlb_cow(struct mm_struct *mm, struct vm_area_struct *vma, struct hstate *h = hstate_vma(vma); struct page *old_page, *new_page; int outside_reserve = 0; + long chg; + bool use_reserve; unsigned long mmun_start; /* For

Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-26 Thread Aneesh Kumar K.V
"Aneesh Kumar K.V" writes: > Joonsoo Kim writes: > >> In order to validate that this failure is reasonable, we need to know >> whether allocation request is for reserved or not on caller function. >> So moving vma_needs_reservation() up to the caller of alloc_huge_page(). >> There is no

Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-26 Thread Aneesh Kumar K.V
Joonsoo Kim writes: > In order to validate that this failure is reasonable, we need to know > whether allocation request is for reserved or not on caller function. > So moving vma_needs_reservation() up to the caller of alloc_huge_page(). > There is no functional change in this patch and

Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-26 Thread Aneesh Kumar K.V
Joonsoo Kim iamjoonsoo@lge.com writes: In order to validate that this failure is reasonable, we need to know whether allocation request is for reserved or not on caller function. So moving vma_needs_reservation() up to the caller of alloc_huge_page(). There is no functional change in this

Re: [PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-26 Thread Aneesh Kumar K.V
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes: Joonsoo Kim iamjoonsoo@lge.com writes: In order to validate that this failure is reasonable, we need to know whether allocation request is for reserved or not on caller function. So moving vma_needs_reservation() up to the caller

[PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-09 Thread Joonsoo Kim
In order to validate that this failure is reasonable, we need to know whether allocation request is for reserved or not on caller function. So moving vma_needs_reservation() up to the caller of alloc_huge_page(). There is no functional change in this patch and following patch use this information.

[PATCH v2 14/20] mm, hugetlb: call vma_needs_reservation before entering alloc_huge_page()

2013-08-09 Thread Joonsoo Kim
In order to validate that this failure is reasonable, we need to know whether allocation request is for reserved or not on caller function. So moving vma_needs_reservation() up to the caller of alloc_huge_page(). There is no functional change in this patch and following patch use this information.