From: Lance Yang <lance.yang@linux.dev>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
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>,
Liam.Howlett@oracle.com,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org
Subject: Re: [PATCH 1/3] mm: mprotect: always skip dma pinned folio in prot_numa_skip()
Date: Tue, 14 Oct 2025 09:42:44 +0800 [thread overview]
Message-ID: <b5f40a6b-482e-4e06-91b3-d6ad0427de85@linux.dev> (raw)
In-Reply-To: <20251013121536.2373249-2-wangkefeng.wang@huawei.com>
On 2025/10/13 20:15, 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>
> ---
LGTM.
Reviewed-by: Lance Yang <lance.yang@linux.dev>
next prev parent reply other threads:[~2025-10-14 1:42 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
2025-10-13 15:49 ` David Hildenbrand
2025-10-14 1:42 ` Lance Yang [this message]
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=b5f40a6b-482e-4e06-91b3-d6ad0427de85@linux.dev \
--to=lance.yang@linux.dev \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.