Recently alloc_buddy_huge_page was renamed to __alloc_buddy_huge_page, so
let's sync comments.
Signed-off-by: Naoya Horiguchi <n-horigu...@ah.jp.nec.com>
---
mm/hugetlb.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git mmotm-2015-10-21-14-41/mm/hugetlb.c
mmotm-2015-10-21-14-41_patched/mm/hugetlb.c
index 9e63f1a..1721c9d 100644
--- mmotm-2015-10-21-14-41/mm/hugetlb.c
+++ mmotm-2015-10-21-14-41_patched/mm/hugetlb.c
@@ -2133,7 +2133,7 @@ static unsigned long set_max_huge_pages(struct hstate *h,
unsigned long count,
* First take pages out of surplus state. Then make up the
* remaining difference by allocating fresh huge pages.
*
- * We might race with alloc_buddy_huge_page() here and be unable
+ * We might race with __alloc_buddy_huge_page() here and be unable
* to convert a surplus huge page to a normal huge page. That is
* not critical, though, it just means the overall size of the
* pool might be one hugepage larger than it needs to be, but
@@ -2175,7 +2175,7 @@ static unsigned long set_max_huge_pages(struct hstate *h,
unsigned long count,
* By placing pages into the surplus state independent of the
* overcommit value, we are allowing the surplus pool size to
* exceed overcommit. There are few sane options here. Since
- * alloc_buddy_huge_page() is checking the global counter,
+ * __alloc_buddy_huge_page() is checking the global counter,
* though, we'll note that we're not allowed to exceed surplus
* and won't grow the pool anywhere else. Not until one of the
* sysctls are changed, or the surplus pages go out of use.
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
