Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759403AbdDSD25 (ORCPT ); Tue, 18 Apr 2017 23:28:57 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:39901 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758837AbdDSD2z (ORCPT ); Tue, 18 Apr 2017 23:28:55 -0400 From: Anshuman Khandual To: linux-kernel@vger.kernel.org, linux-mm@kvack.org Cc: n-horiguchi@ah.jp.nec.com, akpm@linux-foundation.org, aneesh.kumar@linux.vnet.ibm.com Subject: [RFC] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level Date: Wed, 19 Apr 2017 08:57:59 +0530 X-Mailer: git-send-email 2.9.3 X-TM-AS-MML: disable x-cbid: 17041903-0004-0000-0000-000001F632CE X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17041903-0005-0000-0000-000009EA5015 Message-Id: <20170419032759.29700-1-khandual@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-04-19_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=10 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1704190032 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4031 Lines: 117 Though migrating gigantic HugeTLB pages does not sound much like real world use case, they can be affected by memory errors. Hence migration at the PGD level HugeTLB pages should be supported just to enable soft and hard offline use cases. While allocating the new gigantic HugeTLB page, it should not matter whether new page comes from the same node or not. There would be very few gigantic pages on the system afterall, we should not be bothered about node locality when trying to save a big page from crashing. This introduces a new HugeTLB allocator called alloc_gigantic_page() which will scan over all online nodes on the system and allocate a single HugeTLB page. Signed-off-by: Anshuman Khandual --- Tested on a POWER8 machine with 16GB pages along with Aneesh's recent HugeTLB enablement patch series on powerpc which can be found here. https://lkml.org/lkml/2017/4/17/225 Here, we directly call alloc_gigantic_page() which ignores node locality. But we can also first call normal alloc_huge_page() with the node number and if that fails to allocate then call alloc_gigantic_page() as a fallback option. include/linux/hugetlb.h | 8 +++++++- mm/hugetlb.c | 17 +++++++++++++++++ mm/memory-failure.c | 8 ++++++-- 3 files changed, 30 insertions(+), 3 deletions(-) diff --git a/include/linux/hugetlb.h b/include/linux/hugetlb.h index 04b73a9c8b4b..ee75197e6ed8 100644 --- a/include/linux/hugetlb.h +++ b/include/linux/hugetlb.h @@ -347,6 +347,7 @@ struct huge_bootmem_page { struct page *alloc_huge_page(struct vm_area_struct *vma, unsigned long addr, int avoid_reserve); +struct page *alloc_gigantic_page(struct hstate *h); struct page *alloc_huge_page_node(struct hstate *h, int nid); struct page *alloc_huge_page_noerr(struct vm_area_struct *vma, unsigned long addr, int avoid_reserve); @@ -473,7 +474,11 @@ extern int dissolve_free_huge_pages(unsigned long start_pfn, static inline bool hugepage_migration_supported(struct hstate *h) { #ifdef CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION - return huge_page_shift(h) == PMD_SHIFT; + if ((huge_page_shift(h) == PMD_SHIFT) || + (huge_page_shift(h) == PGDIR_SHIFT)) + return true; + else + return false; #else return false; #endif @@ -511,6 +516,7 @@ static inline void hugetlb_count_sub(long l, struct mm_struct *mm) #else /* CONFIG_HUGETLB_PAGE */ struct hstate {}; #define alloc_huge_page(v, a, r) NULL +#define alloc_gigantic_page(h) NULL #define alloc_huge_page_node(h, nid) NULL #define alloc_huge_page_noerr(v, a, r) NULL #define alloc_bootmem_huge_page(h) NULL diff --git a/mm/hugetlb.c b/mm/hugetlb.c index 97a44db06850..f2b31dddb1bc 100644 --- a/mm/hugetlb.c +++ b/mm/hugetlb.c @@ -1669,6 +1669,23 @@ struct page *__alloc_buddy_huge_page_with_mpol(struct hstate *h, return __alloc_buddy_huge_page(h, vma, addr, NUMA_NO_NODE); } +struct page *alloc_gigantic_page(struct hstate *h) +{ + struct page *page = NULL; + int nid = 0; + + spin_lock(&hugetlb_lock); + if (h->free_huge_pages - h->resv_huge_pages > 0) { + for_each_online_node(nid) { + page = dequeue_huge_page_node(h, nid); + if (page) + break; + } + } + spin_unlock(&hugetlb_lock); + return page; +} + /* * This allocation function is useful in the context where vma is irrelevant. * E.g. soft-offlining uses this function because it only cares physical diff --git a/mm/memory-failure.c b/mm/memory-failure.c index fe64d7729a8e..619650969fe5 100644 --- a/mm/memory-failure.c +++ b/mm/memory-failure.c @@ -1481,11 +1481,15 @@ EXPORT_SYMBOL(unpoison_memory); static struct page *new_page(struct page *p, unsigned long private, int **x) { int nid = page_to_nid(p); - if (PageHuge(p)) + if (PageHuge(p)) { + if (hstate_is_gigantic(page_hstate(compound_head(p)))) + return alloc_gigantic_page(page_hstate(compound_head(p))); + return alloc_huge_page_node(page_hstate(compound_head(p)), nid); - else + } else { return __alloc_pages_node(nid, GFP_HIGHUSER_MOVABLE, 0); + } } /* -- 2.12.0