From: Sidhartha Kumar <sidhartha.kumar@oracle.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-mm@kvack.org
Cc: Zi Yan <ziy@nvidia.com>,
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
Subject: Re: [PATCH 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip()
Date: Mon, 13 Oct 2025 11:12:00 -0400 [thread overview]
Message-ID: <1b596590-6562-4c8b-97ab-bb474abd527c@oracle.com> (raw)
In-Reply-To: <20251013121536.2373249-2-wangkefeng.wang@huawei.com>
On 10/13/25 8:15 AM, Kefeng Wang wrote:
> If the folio(even not CoW folio) is dma pinned, it can't be
> migrated, so always skip pinned folio to avoid a waste of cycles
> when folios migration.
>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
Reviewed-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
> ---
> mm/mprotect.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/mm/mprotect.c b/mm/mprotect.c
> index 113b48985834..51a28781de9d 100644
> --- a/mm/mprotect.c
> +++ b/mm/mprotect.c
> @@ -136,9 +136,12 @@ static bool prot_numa_skip(struct vm_area_struct *vma, unsigned long addr,
> if (folio_is_zone_device(folio) || folio_test_ksm(folio))
> goto skip;
>
> - /* Also skip shared copy-on-write pages */
> - if (is_cow_mapping(vma->vm_flags) &&
> - (folio_maybe_dma_pinned(folio) || folio_maybe_mapped_shared(folio)))
> + /* Also skip shared copy-on-write folios */
> + if (is_cow_mapping(vma->vm_flags) && folio_maybe_mapped_shared(folio))
> + goto skip;
> +
> + /* Folios are pinned and can't be migrated */
> + if (folio_maybe_dma_pinned(folio))
> goto skip;
>
> /*
next prev parent reply other threads:[~2025-10-13 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 12:15 [PATCH 0/3] mm: some optimizations for prot numa Kefeng Wang
2025-10-13 12:15 ` [PATCH 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip() Kefeng Wang
2025-10-13 15:12 ` Sidhartha Kumar [this message]
2025-10-13 15:49 ` David Hildenbrand
2025-10-14 1:42 ` Lance Yang
2025-10-13 12:15 ` [PATCH 2/3] mm: mprotect: avoid unnecessary struct page accessing if pte_protnone() Kefeng Wang
2025-10-13 15:22 ` Sidhartha Kumar
2025-10-13 15:53 ` David Hildenbrand
2025-10-14 6:06 ` Kefeng Wang
2025-10-14 7:16 ` David Hildenbrand
2025-10-14 8:02 ` Kefeng Wang
2025-10-14 8:56 ` David Hildenbrand
2025-10-14 9:19 ` Kefeng Wang
2025-10-13 12:15 ` [PATCH 3/3] mm: huge_memory: use prot_numa_skip() for pmd folio Kefeng Wang
2025-10-13 15:41 ` Sidhartha Kumar
2025-10-13 15:58 ` David Hildenbrand
2025-10-14 6:10 ` Kefeng Wang
2025-10-14 7:24 ` David Hildenbrand
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=1b596590-6562-4c8b-97ab-bb474abd527c@oracle.com \
--to=sidhartha.kumar@oracle.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=wangkefeng.wang@huawei.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