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 v5 1/2] mm: Abstract THP allocation
Date: Tue, 24 Sep 2024 20:54:40 +0800 [thread overview]
Message-ID: <d9aff21a-7f37-470d-b798-abd1e354f2da@huawei.com> (raw)
In-Reply-To: <91892582-1063-4757-9cc6-664d57b9d828@arm.com>
On 2024/9/24 20:17, Dev Jain wrote:
>
> On 9/24/24 16:50, Kefeng Wang wrote:
>>
>>
>> On 2024/9/24 18:16, 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,
>>> except that, as David notes at [1], a PMD-aligned address should
>>> be passed to update_mmu_cache_pmd().
>>>
>>> [1]: https://lore.kernel.org/all/ddd3fcd2-48b3-4170-
>>> bcaa-2fe66e093f43@redhat.com/
>>>
>>> Acked-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>>> ---
>>> mm/huge_memory.c | 98 ++++++++++++++++++++++++++++--------------------
>>> 1 file changed, 57 insertions(+), 41 deletions(-)
>>>
>>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>>> index 4e34b7f89daf..bdbf67c18f6c 100644
>>> --- a/mm/huge_memory.c
>>> +++ b/mm/huge_memory.c
>>> @@ -1148,47 +1148,81 @@ 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 *vma_alloc_anon_folio_pmd(struct vm_area_struct
>>> *vma,
>>> + 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;
>>> + unsigned long haddr = addr & HPAGE_PMD_MASK;
>>> + gfp_t gfp = vma_thp_gfp_mask(vma);
>>> + const int order = HPAGE_PMD_ORDER;
>>> + struct folio *folio = vma_alloc_folio(gfp, order, vma, haddr,
>>> true);
>>
>> There is a warning without NUMA,
>>
>> ../mm/huge_memory.c: In function ‘vma_alloc_anon_folio_pmd’:
>> ../mm/huge_memory.c:1154:16: warning: unused variable ‘haddr’ [-
>> Wunused-variable]
>> 1154 | unsigned long haddr = addr & HPAGE_PMD_MASK;
>> | ^~~~~
>>
>
> But why is this happening?
If no CONFIG_NUMA, vma_alloc_folio(...) = folio_alloc_noprof(gfp, order),
it won't use haddr.
next prev parent reply other threads:[~2024-09-24 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 10:16 [PATCH v5 0/2] Do not shatter hugezeropage on wp-fault Dev Jain
2024-09-24 10:16 ` [PATCH v5 1/2] mm: Abstract THP allocation Dev Jain
2024-09-24 11:20 ` Kefeng Wang
2024-09-24 12:17 ` Dev Jain
2024-09-24 12:54 ` Kefeng Wang [this message]
2024-09-25 5:28 ` Dev Jain
2024-09-24 10:16 ` [PATCH v5 2/2] mm: Allocate THP on hugezeropage wp-fault Dev Jain
2024-09-24 12:20 ` David Hildenbrand
2024-09-24 13:13 ` Kefeng Wang
2024-09-25 5:31 ` Dev Jain
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=d9aff21a-7f37-470d-b798-abd1e354f2da@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