linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	<linux-mm@kvack.org>, Baolin Wang <baolin.wang@linux.alibaba.com>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
	<Liam.Howlett@oracle.com>,
	Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [PATCH v3 2/3] mm: mprotect: avoid unnecessary struct page accessing if pte_protnone()
Date: Thu, 16 Oct 2025 09:35:29 +0800	[thread overview]
Message-ID: <9c8834d0-cdc2-4c04-bc9d-0bab5ae26f76@huawei.com> (raw)
In-Reply-To: <DAF946DE-0D7A-4B15-BF28-BF6464ADFD2F@nvidia.com>



On 2025/10/16 9:28, Zi Yan wrote:
> On 15 Oct 2025, at 8:35, Kefeng Wang wrote:
> 
>> If the pte_protnone() is true, we could avoid unnecessary struct page
>> accessing and reduce cache footprint when scanning page tables for prot
>> numa, the performance test of pmbench memory accessing benchmark
>> should be benifit, see more commit a818f5363a0e ("autonuma: reduce cache
>> footprint when scanning page tables").
>>
>> Reviewed-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>   mm/mprotect.c | 30 +++++++++++++-----------------
>>   1 file changed, 13 insertions(+), 17 deletions(-)
>>
>> diff --git a/mm/mprotect.c b/mm/mprotect.c
>> index bb59a42809b8..ed44aadb7aaa 100644
>> --- a/mm/mprotect.c
>> +++ b/mm/mprotect.c
>> @@ -118,18 +118,13 @@ static int mprotect_folio_pte_batch(struct folio *folio, pte_t *ptep,
>>   	return folio_pte_batch_flags(folio, NULL, ptep, &pte, max_nr_ptes, flags);
>>   }
>>
>> -static bool prot_numa_skip(struct vm_area_struct *vma, unsigned long addr,
>> -			   pte_t oldpte, pte_t *pte, int target_node,
>> -			   struct folio *folio)
>> +static bool prot_numa_skip(struct vm_area_struct *vma, int target_node,
>> +		struct folio *folio)
>>   {
>>   	bool ret = true;
>>   	bool toptier;
>>   	int nid;
>>
>> -	/* Avoid TLB flush if possible */
>> -	if (pte_protnone(oldpte))
>> -		goto skip;
>> -
>>   	if (!folio)
>>   		goto skip;
>>
>> @@ -307,23 +302,24 @@ static long change_pte_range(struct mmu_gather *tlb,
>>   			struct page *page;
>>   			pte_t ptent;
>>
>> +			/* Already in the desired state. */
>> +			if (prot_numa && pte_protnone(oldpte))
>> +				continue;
> 
> For a folio pte batch, instead of calculating nr_ptes to skip, this just
> skip PTEs one by one. Looking at folio_pte_batch_flags(), this way looks
> better.

folio_pte_batch_flags need a folio, we want to avoid it,
maybe use pte_batch_hint() here.

> 
>> +
>>   			page = vm_normal_page(vma, addr, oldpte);
>>   			if (page)
>>   				folio = page_folio(page);
>> +
>>   			/*
>>   			 * Avoid trapping faults against the zero or KSM
>>   			 * pages. See similar comment in change_huge_pmd.
>>   			 */
>> -			if (prot_numa) {
>> -				int ret = prot_numa_skip(vma, addr, oldpte, pte,
>> -							 target_node, folio);
>> -				if (ret) {
>> -
>> -					/* determine batch to skip */
>> -					nr_ptes = mprotect_folio_pte_batch(folio,
>> -						  pte, oldpte, max_nr_ptes, /* flags = */ 0);
>> -					continue;
>> -				}
>> +			if (prot_numa && prot_numa_skip(vma, target_node,
>> +							folio)) {
>> +				/* determine batch to skip */
>> +				nr_ptes = mprotect_folio_pte_batch(folio,
>> +					  pte, oldpte, max_nr_ptes, /* flags = */ 0);
>> +				continue;
>>   			}
>>
>>   			nr_ptes = mprotect_folio_pte_batch(folio, pte, oldpte, max_nr_ptes, flags);
> 
> Acked-by: Zi Yan <ziy@nvidia.com>

Thanks.
> 
> --
> Best Regards,
> Yan, Zi
> 



  reply	other threads:[~2025-10-16  1:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 12:35 [PATCH v3 0/3] mm: some optimizations for prot numa Kefeng Wang
2025-10-15 12:35 ` [PATCH v3 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip() Kefeng Wang
2025-10-15 15:32   ` Lorenzo Stoakes
2025-10-16  1:00     ` Kefeng Wang
2025-10-16 21:10       ` Andrew Morton
2025-10-17  8:46         ` Lorenzo Stoakes
2025-10-17 14:12         ` Kefeng Wang
2025-10-16  1:14   ` Zi Yan
2025-10-16 17:53   ` Dev Jain
2025-10-15 12:35 ` [PATCH v3 2/3] mm: mprotect: avoid unnecessary struct page accessing if pte_protnone() Kefeng Wang
2025-10-15 15:43   ` Lorenzo Stoakes
2025-10-15 17:45     ` David Hildenbrand
2025-10-16  1:07       ` Kefeng Wang
2025-10-17  8:47         ` Lorenzo Stoakes
2025-10-17  8:46       ` Lorenzo Stoakes
2025-10-16  1:28   ` Zi Yan
2025-10-16  1:35     ` Kefeng Wang [this message]
2025-10-16 18:02   ` Dev Jain
2025-10-15 12:35 ` [PATCH v3 3/3] mm: huge_memory: use folio_needs_prot_numa() for pmd folio Kefeng Wang
2025-10-16 19:19   ` David Hildenbrand
2025-10-17 10:07   ` Lorenzo Stoakes
2025-10-17 14:13     ` Kefeng Wang

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=9c8834d0-cdc2-4c04-bc9d-0bab5ae26f76@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=ryan.roberts@arm.com \
    --cc=sidhartha.kumar@oracle.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