From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Dev Jain <dev.jain@arm.com>, <akpm@linux-foundation.org>,
<david@redhat.com>, <willy@infradead.org>,
<kirill.shutemov@linux.intel.com>
Cc: <ryan.roberts@arm.com>, <anshuman.khandual@arm.com>,
<catalin.marinas@arm.com>, <cl@gentwo.org>, <vbabka@suse.cz>,
<mhocko@suse.com>, <apopple@nvidia.com>,
<dave.hansen@linux.intel.com>, <will@kernel.org>,
<baohua@kernel.org>, <jack@suse.cz>, <mark.rutland@arm.com>,
<hughd@google.com>, <aneesh.kumar@kernel.org>,
<yang@os.amperecomputing.com>, <peterx@redhat.com>,
<ioworker0@gmail.com>, <jglisse@google.com>, <ziy@nvidia.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v3 1/2] mm: Abstract THP allocation
Date: Wed, 11 Sep 2024 18:52:43 +0800 [thread overview]
Message-ID: <170988b0-db8a-4612-a70c-b20ea2d4c020@huawei.com> (raw)
In-Reply-To: <20240911065600.1002644-2-dev.jain@arm.com>
On 2024/9/11 14:55, Dev Jain wrote:
> In preparation for the second patch, abstract away the THP allocation
> logic present in the create_huge_pmd() path, which corresponds to the
> faulting case when no page is present.
>
> There should be no functional change as a result of applying
> this patch.
>
> Signed-off-by: Dev Jain <dev.jain@arm.com>
> ---
> mm/huge_memory.c | 110 +++++++++++++++++++++++++++++------------------
> 1 file changed, 67 insertions(+), 43 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index 67c86a5d64a6..b96a1ff2bf40 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -943,47 +943,88 @@ unsigned long thp_get_unmapped_area(struct file *filp, unsigned long addr,
> }
> EXPORT_SYMBOL_GPL(thp_get_unmapped_area);
>
> -static vm_fault_t __do_huge_pmd_anonymous_page(struct vm_fault *vmf,
> - struct page *page, gfp_t gfp)
> +static struct folio *pmd_thp_fault_alloc(gfp_t gfp, struct vm_area_struct *vma,
> + unsigned long haddr, unsigned long addr)
> {
> - struct vm_area_struct *vma = vmf->vma;
> - struct folio *folio = page_folio(page);
> - pgtable_t pgtable;
> - unsigned long haddr = vmf->address & HPAGE_PMD_MASK;
> - vm_fault_t ret = 0;
> + const int order = HPAGE_PMD_ORDER;
Maybe move vma_thp_gfp_mask() into this function too.
> + struct folio *folio = vma_alloc_folio(gfp, order, vma, haddr, true);
>
> - VM_BUG_ON_FOLIO(!folio_test_large(folio), folio);
> + if (unlikely(!folio)) {
> + count_vm_event(THP_FAULT_FALLBACK);
> + count_mthp_stat(order, MTHP_STAT_ANON_FAULT_FALLBACK);
> + goto out;
> + }
>
> + VM_BUG_ON_FOLIO(!folio_test_large(folio), folio);
> if (mem_cgroup_charge(folio, vma->vm_mm, gfp)) {
> folio_put(folio);
> count_vm_event(THP_FAULT_FALLBACK);
> count_vm_event(THP_FAULT_FALLBACK_CHARGE);
> - count_mthp_stat(HPAGE_PMD_ORDER, MTHP_STAT_ANON_FAULT_FALLBACK);
> - count_mthp_stat(HPAGE_PMD_ORDER, MTHP_STAT_ANON_FAULT_FALLBACK_CHARGE);
> - return VM_FAULT_FALLBACK;
> + count_mthp_stat(order, MTHP_STAT_ANON_FAULT_FALLBACK);
> + count_mthp_stat(order, MTHP_STAT_ANON_FAULT_FALLBACK_CHARGE);
> + goto out;
We need to return NULL here as folio not set to null,
> }
> folio_throttle_swaprate(folio, gfp);
>
> - pgtable = pte_alloc_one(vma->vm_mm);
> - if (unlikely(!pgtable)) {
> - ret = VM_FAULT_OOM;
> - goto release;
> - }
> -
> - folio_zero_user(folio, vmf->address);
> + folio_zero_user(folio, addr);
> /*
> * The memory barrier inside __folio_mark_uptodate makes sure that
> * folio_zero_user writes become visible before the set_pmd_at()
> * write.
> */
> __folio_mark_uptodate(folio);
> +out:
> + return folio;
> +}
> +
next prev parent reply other threads:[~2024-09-11 10:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 6:55 [PATCH v3 0/2] Do not shatter hugezeropage on wp-fault Dev Jain
2024-09-11 6:55 ` [PATCH v3 1/2] mm: Abstract THP allocation Dev Jain
2024-09-11 9:27 ` David Hildenbrand
2024-09-11 9:29 ` David Hildenbrand
2024-09-11 12:02 ` Dev Jain
2024-09-11 12:00 ` Dev Jain
2024-09-11 12:35 ` David Hildenbrand
2024-09-11 12:55 ` Dev Jain
2024-09-11 12:53 ` Dev Jain
2024-09-11 13:00 ` David Hildenbrand
2024-09-11 13:05 ` Dev Jain
2024-09-11 13:14 ` David Hildenbrand
2024-09-11 13:16 ` Dev Jain
2024-09-11 10:52 ` Kefeng Wang [this message]
2024-09-11 12:22 ` Dev Jain
2024-09-12 13:26 ` kernel test robot
2024-09-11 6:56 ` [PATCH v3 2/2] mm: Allocate THP on hugezeropage wp-fault Dev Jain
2024-09-11 9:36 ` David Hildenbrand
2024-09-11 12:10 ` Dev Jain
2024-09-11 12:36 ` David Hildenbrand
2024-09-12 15:44 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170988b0-db8a-4612-a70c-b20ea2d4c020@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=baohua@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@gentwo.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=hughd@google.com \
--cc=ioworker0@gmail.com \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox