[Patch v4 1/7] mm/hugetlb: not necessary to coalesce regions recursively

[Wei Yang]

Per my understanding, we keep the regions ordered and would always
coalesce regions properly. So the task to keep this property is just
to coalesce its neighbour.

Let's simplify this.

Signed-off-by: Wei Yang <richard.weiy...@linux.alibaba.com>
Reviewed-by: Baoquan He <b...@redhat.com>
Reviewed-by: Mike Kravetz <mike.krav...@oracle.com>
---
 mm/hugetlb.c | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index a301c2d672bf..db6af2654f12 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -309,8 +309,7 @@ static void coalesce_file_region(struct resv_map *resv, 
struct file_region *rg)
                list_del(&rg->link);
                kfree(rg);
 
-               coalesce_file_region(resv, prg);
-               return;
+               rg = prg;
        }
 
        nrg = list_next_entry(rg, link);
@@ -320,9 +319,6 @@ static void coalesce_file_region(struct resv_map *resv, 
struct file_region *rg)
 
                list_del(&rg->link);
                kfree(rg);
-
-               coalesce_file_region(resv, nrg);
-               return;
        }
 }
 
-- 
2.20.1 (Apple Git-117)