From: Zi Yan <zi.yan@sent.com>
To: David Hildenbrand <david@redhat.com>,
"Huang, Ying" <ying.huang@intel.com>,
linux-mm@kvack.org
Cc: Zi Yan <ziy@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/3] Fix and refactor do_{huge_pmd_}numa_page()
Date: Thu, 11 Jul 2024 22:44:52 -0400 [thread overview]
Message-ID: <20240712024455.163543-1-zi.yan@sent.com> (raw)
From: Zi Yan <ziy@nvidia.com>
First patch adds the missing sysctl_numa_balancing_mode check. Second patch
introduces folio_has_cpupid() to replace open coded folio last_cpupid check.
Third patch consolidates code in do_numa_page() and do_huge_pmd_numa_page()
by moving more common code into numa_migrate_prep() (renamed to
numa_migrate_check() in the patch).
The RFC is mainly for third patch. It changes the original code behavior:
1. do_huge_pmd_numa_page() did not check shared folios to set TNF_SHARED.
2. do_huge_pmd_numa_page() did not check and skip zone device folios.
Zi Yan (3):
memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page()
memory tiering: introduce folio_has_cpupid() check
mm/migrate: move common code to numa_migrate_check (was
numa_migrate_prep)
include/linux/memory-tiers.h | 8 ++++
kernel/sched/fair.c | 3 +-
mm/huge_memory.c | 31 +++++---------
mm/internal.h | 5 ++-
mm/memory-tiers.c | 17 ++++++++
mm/memory.c | 82 +++++++++++++++++-------------------
mm/mprotect.c | 3 +-
7 files changed, 80 insertions(+), 69 deletions(-)
--
2.43.0
next reply other threads:[~2024-07-12 2:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 2:44 Zi Yan [this message]
2024-07-12 2:44 ` [RFC PATCH 1/3] memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page() Zi Yan
2024-07-12 3:22 ` Huang, Ying
2024-07-12 4:01 ` Baolin Wang
2024-07-13 1:13 ` David Hildenbrand
2024-07-13 1:18 ` Zi Yan
2024-07-13 1:23 ` David Hildenbrand
2024-07-12 2:44 ` [RFC PATCH 2/3] memory tiering: introduce folio_has_cpupid() check Zi Yan
2024-07-12 6:27 ` Huang, Ying
2024-07-12 2:44 ` [RFC PATCH 3/3] mm/migrate: move common code to numa_migrate_check (was numa_migrate_prep) Zi Yan
2024-07-18 8:36 ` Huang, Ying
2024-07-18 14:40 ` Zi Yan
2024-07-19 20:19 ` Zi Yan
2024-07-22 1:47 ` Huang, Ying
2024-07-22 14:01 ` Zi Yan
2024-07-22 15:21 ` Zi Yan
2024-07-23 1:16 ` Huang, Ying
2024-07-23 1:43 ` Zi Yan
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=20240712024455.163543-1-zi.yan@sent.com \
--to=zi.yan@sent.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ying.huang@intel.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