From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B9BB6C433E0 for ; Fri, 19 Feb 2021 10:52:01 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id B53ED64EBD for ; Fri, 19 Feb 2021 10:52:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B53ED64EBD Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=bytedance.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 2E5998D000F; Fri, 19 Feb 2021 05:52:00 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 2700B8D000A; Fri, 19 Feb 2021 05:52:00 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 138628D000F; Fri, 19 Feb 2021 05:52:00 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0129.hostedemail.com [216.40.44.129]) by kanga.kvack.org (Postfix) with ESMTP id E246C8D000A for ; Fri, 19 Feb 2021 05:51:59 -0500 (EST) Received: from smtpin04.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 86F0318179031 for ; Fri, 19 Feb 2021 10:51:59 +0000 (UTC) X-FDA: 77834702358.04.0D3AA1E Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) by imf21.hostedemail.com (Postfix) with ESMTP id 6452CE0011F3 for ; Fri, 19 Feb 2021 10:51:55 +0000 (UTC) Received: by mail-pg1-f174.google.com with SMTP id n10so3754941pgl.10 for ; Fri, 19 Feb 2021 02:51:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=KiQuVZ3avVzNbFJ1x3B7dVdZYg6752ZUss1NEmBrEgM=; b=km91PGmU/O3EsVX8zIW81Qm3W6gNYW7s+AD+AgrskmJ5qTj5t7LD+4gESDvMHMbgJ1 UydR8UortJ+imWTHBT6mBhG/84D9BcRR4kEwY+YhpTIXGy9ojz/dnQmq1aT+Cnk5JAPZ 7s8OE/8b2d9DmFN9DchTrTRqrcAKi7Dyv5o5/zpbycpvLWCivS7bkf+5598pPki7bLVB 5vG1s7l4FbT4zRTXFpesPjrqZxtWl8mREWG/7PuufIGQlkgq5ouDdUbrfTPLkfQ655RJ pqm/QK8wvGCWvWmTn4R5gRCsL2gEMaP5yPLnCMf32xd+/iBzC8psKM7obENRb8pLEIlX F8Bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=KiQuVZ3avVzNbFJ1x3B7dVdZYg6752ZUss1NEmBrEgM=; b=K5GZblb8xpTgKdy0IbhFJOFHOQv6sdpAROJ1hKpDH2S4fZqxqcsnixbc4p1mv8s2ot LYX1iFS/GRBji/TLq5SSHXmevR8z0lDVZr7k4tmv1ws/fJKr4WhF9gmKCBMWkaDuzenW pWmDJiMTQeEz8/QsDAtHykWPgPwfjznDEDaqil7GklXvClDoDNuXSZFx5M7PTvyqZjuT 3FV55swzR20131hmEVNJgnSW6UfB57x6dSSHuc6kS5eGgiYNxxI6Mgy5gbUgq2QRLezh VUZkHHt7mbonWLlu5Xf5pgJsxTDI8mTu6i49mu5XC1rCrQsLKqvGTwwUpH73ZI2XqEWV xG8A== X-Gm-Message-State: AOAM533JgBdViYaodExqb1VU14MCYuN0UjFC8fxxgnHxISQuNRQkD9eJ tN6mY/4MVIprR1xh8P2zggGb0g== X-Google-Smtp-Source: ABdhPJzfW9DpI4DVFIoO0Yc50BItwZU+8YPUiiAQAjyV01QY2vnH2q0LC5GFpudZROsDg6Pt3IDUoQ== X-Received: by 2002:a63:ce4b:: with SMTP id r11mr8085413pgi.148.1613731915832; Fri, 19 Feb 2021 02:51:55 -0800 (PST) Received: from localhost.localdomain ([139.177.225.250]) by smtp.gmail.com with ESMTPSA id x1sm9662193pgj.37.2021.02.19.02.51.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Feb 2021 02:51:55 -0800 (PST) From: Muchun Song To: corbet@lwn.net, mike.kravetz@oracle.com, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com, dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org, viro@zeniv.linux.org.uk, akpm@linux-foundation.org, paulmck@kernel.org, mchehab+huawei@kernel.org, pawan.kumar.gupta@linux.intel.com, rdunlap@infradead.org, oneukum@suse.com, anshuman.khandual@arm.com, jroedel@suse.de, almasrymina@google.com, rientjes@google.com, willy@infradead.org, osalvador@suse.de, mhocko@suse.com, song.bao.hua@hisilicon.com, david@redhat.com, naoya.horiguchi@nec.com, joao.m.martins@oracle.com Cc: duanxiongchun@bytedance.com, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Muchun Song Subject: [PATCH v16 0/9] Free some vmemmap pages of HugeTLB page Date: Fri, 19 Feb 2021 18:49:45 +0800 Message-Id: <20210219104954.67390-1-songmuchun@bytedance.com> X-Mailer: git-send-email 2.21.0 (Apple Git-122) MIME-Version: 1.0 X-Stat-Signature: nw3gz1trxwb1fowqhcga5owyjrnk6n8d X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 6452CE0011F3 Received-SPF: none (bytedance.com>: No applicable sender policy available) receiver=imf21; identity=mailfrom; envelope-from=""; helo=mail-pg1-f174.google.com; client-ip=209.85.215.174 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1613731915-880968 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi all, This patch series will free some vmemmap pages(struct page structures) associated with each hugetlbpage when preallocated to save memory. In order to reduce the difficulty of the first version of code review. >From this version, we disable PMD/huge page mapping of vmemmap if this feature was enabled. This accutualy eliminate a bunch of the complex code doing page table manipulation. When this patch series is solid, we cam ad= d the code of vmemmap page table manipulation in the future. The struct page structures (page structs) are used to describe a physical page frame. By default, there is a one-to-one mapping from a page frame t= o it's corresponding page struct. The HugeTLB pages consist of multiple base page size pages and is support= ed by many architectures. See hugetlbpage.rst in the Documentation directory for more details. On the x86 architecture, HugeTLB pages of size 2MB and = 1GB are currently supported. Since the base page size on x86 is 4KB, a 2MB HugeTLB page consists of 512 base pages and a 1GB HugeTLB page consists o= f 4096 base pages. For each base page, there is a corresponding page struct= . Within the HugeTLB subsystem, only the first 4 page structs are used to contain unique information about a HugeTLB page. HUGETLB_CGROUP_MIN_ORDER provides this upper limit. The only 'useful' information in the remaining page structs is the compound_head field, and this field is the same for a= ll tail pages. By removing redundant page structs for HugeTLB pages, memory can returned= to the buddy allocator for other uses. When the system boot up, every 2M HugeTLB has 512 struct page structs whi= ch size is 8 pages(sizeof(struct page) * 512 / PAGE_SIZE). HugeTLB struct pages(8 pages) page frame(8 p= ages) +-----------+ ---virt_to_page---> +-----------+ mapping to +--------= ---+ | | | 0 | -------------> | 0 = | | | +-----------+ +--------= ---+ | | | 1 | -------------> | 1 = | | | +-----------+ +--------= ---+ | | | 2 | -------------> | 2 = | | | +-----------+ +--------= ---+ | | | 3 | -------------> | 3 = | | | +-----------+ +--------= ---+ | | | 4 | -------------> | 4 = | | 2MB | +-----------+ +--------= ---+ | | | 5 | -------------> | 5 = | | | +-----------+ +--------= ---+ | | | 6 | -------------> | 6 = | | | +-----------+ +--------= ---+ | | | 7 | -------------> | 7 = | | | +-----------+ +--------= ---+ | | | | | | +-----------+ The value of page->compound_head is the same for all tail pages. The firs= t page of page structs (page 0) associated with the HugeTLB page contains t= he 4 page structs necessary to describe the HugeTLB. The only use of the remai= ning pages of page structs (page 1 to page 7) is to point to page->compound_he= ad. Therefore, we can remap pages 2 to 7 to page 1. Only 2 pages of page stru= cts will be used for each HugeTLB page. This will allow us to free the remain= ing 6 pages to the buddy allocator. Here is how things look after remapping. HugeTLB struct pages(8 pages) page frame(8 p= ages) +-----------+ ---virt_to_page---> +-----------+ mapping to +--------= ---+ | | | 0 | -------------> | 0 = | | | +-----------+ +--------= ---+ | | | 1 | -------------> | 1 = | | | +-----------+ +--------= ---+ | | | 2 | ----------------^ ^ ^ ^ = ^ ^ | | +-----------+ | | | = | | | | | 3 | ------------------+ | | = | | | | +-----------+ | | = | | | | | 4 | --------------------+ | = | | | 2MB | +-----------+ | = | | | | | 5 | ----------------------+ = | | | | +-----------+ = | | | | | 6 | ------------------------= + | | | +-----------+ = | | | | 7 | ------------------------= --+ | | +-----------+ | | | | | | +-----------+ When a HugeTLB is freed to the buddy system, we should allocate 6 pages f= or vmemmap pages and restore the previous mapping relationship. Apart from 2MB HugeTLB page, we also have 1GB HugeTLB page. It is similar to the 2MB HugeTLB page. We also can use this approach to free the vmemma= p pages. In this case, for the 1GB HugeTLB page, we can save 4094 pages. This is a very substantial gain. On our server, run some SPDK/QEMU applications whi= ch will use 1024GB hugetlbpage. With this feature enabled, we can save ~16GB (1G hugepage)/~12GB (2MB hugepage) memory. Because there are vmemmap page tables reconstruction on the freeing/alloc= ating path, it increases some overhead. Here are some overhead analysis. 1) Allocating 10240 2MB hugetlb pages. a) With this patch series applied: # time echo 10240 > /proc/sys/vm/nr_hugepages real 0m0.166s user 0m0.000s sys 0m0.166s # bpftrace -e 'kprobe:alloc_fresh_huge_page { @start[tid] =3D nsecs; } kretprobe:alloc_fresh_huge_page /@start[tid]/ { @latency =3D hist(ns= ecs - @start[tid]); delete(@start[tid]); }' Attaching 2 probes... @latency: [8K, 16K) 5476 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@| [16K, 32K) 4760 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @ | [32K, 64K) 4 | = | b) Without this patch series: # time echo 10240 > /proc/sys/vm/nr_hugepages real 0m0.067s user 0m0.000s sys 0m0.067s # bpftrace -e 'kprobe:alloc_fresh_huge_page { @start[tid] =3D nsecs; } kretprobe:alloc_fresh_huge_page /@start[tid]/ { @latency =3D hist(ns= ecs - @start[tid]); delete(@start[tid]); }' Attaching 2 probes... @latency: [4K, 8K) 10147 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@| [8K, 16K) 93 | = | Summarize: this feature is about ~2x slower than before. 2) Freeing 10240 2MB hugetlb pages. a) With this patch series applied: # time echo 0 > /proc/sys/vm/nr_hugepages real 0m0.213s user 0m0.000s sys 0m0.213s # bpftrace -e 'kprobe:free_pool_huge_page { @start[tid] =3D nsecs; } kretprobe:free_pool_huge_page /@start[tid]/ { @latency =3D hist(nsec= s - @start[tid]); delete(@start[tid]); }' Attaching 2 probes... @latency: [8K, 16K) 6 | = | [16K, 32K) 10227 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@| [32K, 64K) 7 | = | b) Without this patch series: # time echo 0 > /proc/sys/vm/nr_hugepages real 0m0.081s user 0m0.000s sys 0m0.081s # bpftrace -e 'kprobe:free_pool_huge_page { @start[tid] =3D nsecs; } kretprobe:free_pool_huge_page /@start[tid]/ { @latency =3D hist(nsec= s - @start[tid]); delete(@start[tid]); }' Attaching 2 probes... @latency: [4K, 8K) 6805 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@= @@@@@@@@| [8K, 16K) 3427 |@@@@@@@@@@@@@@@@@@@@@@@@@@ = | [16K, 32K) 8 | = | Summarize: The overhead of __free_hugepage is about ~2-3x slower than = before. Although the overhead has increased, the overhead is not significant. Lik= e Mike said, "However, remember that the majority of use cases create hugetlb pa= ges at or shortly after boot time and add them to the pool. So, additional overh= ead is at pool creation time. There is no change to 'normal run time' operations= of getting a page from or returning a page to the pool (think page fault/unm= ap)". Despite the overhead and in addition to the memory gains from this series= . The following data is obtained by Joao Martins. Very thanks to his effort. There's an additional benefit which is page (un)pinners will see an impro= vement and Joao presumes because there are fewer memmap pages and thus the tail/= head pages are staying in cache more often. Out of the box Joao saw (when comparing linux-next against linux-next + t= his series) with gup_test and pinning a 16G hugetlb file (with 1G pages): get_user_pages(): ~32k -> ~9k unpin_user_pages(): ~75k -> ~70k Usually any tight loop fetching compound_head(), or reading tail pages da= ta (e.g. compound_head) benefit a lot. There's some unpinning inefficiencies Joao = was fixing[0], but with that in added it shows even more: unpin_user_pages(): ~27k -> ~3.8k [0] https://lore.kernel.org/linux-mm/20210204202500.26474-1-joao.m.martin= s@oracle.com/ Todo: - Free all of the tail vmemmap pages Now for the 2MB HugrTLB page, we only free 6 vmemmap pages. we really= can free 7 vmemmap pages. In this case, we can see 8 of the 512 struct pa= ge structures has beed set PG_head flag. If we can adjust compound_head(= ) slightly and make compound_head() return the real head struct page wh= en the parameter is the tail struct page but with PG_head flag set. In order to make the code evolution route clearer. This feature can c= an be a separate patch after this patchset is solid. - Support for other architectures (e.g. aarch64). - Enable PMD/huge page mapping of vmemmap even if this feature was enab= led. Changelog in v15 -> v16: - Use GFP_KERNEL to allocate vmemmap pages. Thanks to Mike, David H and Michal's suggestions. Changelog in v14 -> v15: - Fix some issues suggested by Oscar. Thanks to Oscar. - Add numbers which Joao Martins tested to cover letter. Thanks to his = effort. Changelog in v13 -> v14: - Refuse to free the HugeTLB page when the system is under memory press= ure. - Use GFP_ATOMIC to allocate vmemmap pages instead of GFP_KERNEL. - Rebase to linux-next 20210202. - Fix and add some comments for vmemmap_remap_free(). Thanks to Oscar, Mike, David H and David R's suggestions and review. Changelog in v12 -> v13: - Remove VM_WARN_ON_PAGE macro. - Add more comments in vmemmap_pte_range() and vmemmap_remap_free(). Thanks to Oscar and Mike's suggestions and review. Changelog in v11 -> v12: - Move VM_WARN_ON_PAGE to a separate patch. - Call __free_hugepage() with hugetlb_lock (See patch #5.) to serialize with dissolve_free_huge_page(). It is to prepare for patch #9. - Introduce PageHugeInflight. See patch #9. Changelog in v10 -> v11: - Fix compiler error when !CONFIG_HUGETLB_PAGE_FREE_VMEMMAP. - Rework some comments and commit changes. - Rework vmemmap_remap_free() to 3 parameters. Thanks to Oscar and Mike's suggestions and review. Changelog in v9 -> v10: - Fix a bug in patch #11. Thanks to Oscar for pointing that out. - Rework some commit log or comments. Thanks Mike and Oscar for the sug= gestions. - Drop VMEMMAP_TAIL_PAGE_REUSE in the patch #3. Thank you very much Mike and Oscar for reviewing the code. Changelog in v8 -> v9: - Rework some code. Very thanks to Oscar. - Put all the non-hugetlb vmemmap functions under sparsemem-vmemmap.c. Changelog in v7 -> v8: - Adjust the order of patches. Very thanks to David and Oscar. Your suggestions are very valuable. Changelog in v6 -> v7: - Rebase to linux-next 20201130 - Do not use basepage mapping for vmemmap when this feature is disabled= . - Rework some patchs. [PATCH v6 08/16] mm/hugetlb: Free the vmemmap pages associated with e= ach hugetlb page [PATCH v6 10/16] mm/hugetlb: Allocate the vmemmap pages associated wi= th each hugetlb page Thanks to Oscar and Barry. Changelog in v5 -> v6: - Disable PMD/huge page mapping of vmemmap if this feature was enabled. - Simplify the first version code. Changelog in v4 -> v5: - Rework somme comments and code in the [PATCH v4 04/21] and [PATCH v4 = 05/21]. Thanks to Mike and Oscar's suggestions. Changelog in v3 -> v4: - Move all the vmemmap functions to hugetlb_vmemmap.c. - Make the CONFIG_HUGETLB_PAGE_FREE_VMEMMAP default to y, if we want to disable this feature, we should disable it by a boot/kernel command l= ine. - Remove vmemmap_pgtable_{init, deposit, withdraw}() helper functions. - Initialize page table lock for vmemmap through core_initcall mechanis= m. Thanks for Mike and Oscar's suggestions. Changelog in v2 -> v3: - Rename some helps function name. Thanks Mike. - Rework some code. Thanks Mike and Oscar. - Remap the tail vmemmap page with PAGE_KERNEL_RO instead of PAGE_KERNE= L. Thanks Matthew. - Add some overhead analysis in the cover letter. - Use vmemap pmd table lock instead of a hugetlb specific global lock. Changelog in v1 -> v2: - Fix do not call dissolve_compound_page in alloc_huge_page_vmemmap(). - Fix some typo and code style problems. - Remove unused handle_vmemmap_fault(). - Merge some commits to one commit suggested by Mike. Muchun Song (9): mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c mm: hugetlb: introduce a new config HUGETLB_PAGE_FREE_VMEMMAP mm: hugetlb: free the vmemmap pages associated with each HugeTLB page mm: hugetlb: alloc the vmemmap pages associated with each HugeTLB page mm: hugetlb: set the PageHWPoison to the raw error page mm: hugetlb: add a kernel parameter hugetlb_free_vmemmap mm: hugetlb: introduce nr_free_vmemmap_pages in the struct hstate mm: hugetlb: gather discrete indexes of tail page mm: hugetlb: optimize the code with the help of the compiler Documentation/admin-guide/kernel-parameters.txt | 14 ++ Documentation/admin-guide/mm/hugetlbpage.rst | 12 + arch/x86/mm/init_64.c | 13 +- fs/Kconfig | 6 + include/linux/bootmem_info.h | 65 ++++++ include/linux/hugetlb.h | 47 +++- include/linux/hugetlb_cgroup.h | 19 +- include/linux/memory_hotplug.h | 27 --- include/linux/mm.h | 5 + mm/Makefile | 2 + mm/bootmem_info.c | 124 ++++++++++ mm/hugetlb.c | 166 +++++++++++--- mm/hugetlb_vmemmap.c | 293 ++++++++++++++++++= ++++++ mm/hugetlb_vmemmap.h | 51 +++++ mm/memory_hotplug.c | 116 ---------- mm/sparse-vmemmap.c | 280 ++++++++++++++++++= ++++ mm/sparse.c | 1 + 17 files changed, 1054 insertions(+), 187 deletions(-) create mode 100644 include/linux/bootmem_info.h create mode 100644 mm/bootmem_info.c create mode 100644 mm/hugetlb_vmemmap.c create mode 100644 mm/hugetlb_vmemmap.h --=20 2.11.0