From: Barry Song <21cnbao@gmail.com>
To: wangkefeng.wang@huawei.com
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org,
baohua@kernel.org, baolin.wang@linux.alibaba.com,
david@redhat.com, dev.jain@arm.com, lance.yang@linux.dev,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
ryan.roberts@arm.com, sidhartha.kumar@oracle.com, ziy@nvidia.com
Subject: Re: [PATCH v2 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip()
Date: Wed, 15 Oct 2025 06:20:03 +0800 [thread overview]
Message-ID: <20251014222003.1358-1-21cnbao@gmail.com> (raw)
In-Reply-To: <20251014113349.2618158-2-wangkefeng.wang@huawei.com>
> 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.
>
> Reviewed-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: Lance Yang <lance.yang@linux.dev>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
LGTM,
Reviewed-by: Barry Song <baohua@kernel.org>
> ---
> mm/mprotect.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2025-10-14 22:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 11:33 [PATCH v2 0/3] mm: some optimizations for prot numa Kefeng Wang
2025-10-14 11:33 ` [PATCH v2 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip() Kefeng Wang
2025-10-14 22:20 ` Barry Song [this message]
2025-10-14 11:33 ` [PATCH v2 2/3] mm: mprotect: avoid unnecessary struct page accessing if pte_protnone() Kefeng Wang
2025-10-14 12:13 ` David Hildenbrand
2025-10-15 7:32 ` Dev Jain
2025-10-15 8:50 ` Kefeng Wang
2025-10-14 11:33 ` [PATCH v2 3/3] mm: huge_memory: use folio_skip_prot_numa() for pmd folio Kefeng Wang
2025-10-15 7:30 ` Dev Jain
2025-10-15 9:21 ` Kefeng Wang
2025-10-15 9:54 ` David Hildenbrand
2025-10-15 11:04 ` Kefeng Wang
2025-10-15 11:30 ` David Hildenbrand
2025-10-15 12:37 ` 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=20251014222003.1358-1-21cnbao@gmail.com \
--to=21cnbao@gmail.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=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