From: Zi Yan <ziy@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Cc: David Hildenbrand <david@redhat.com>,
"Huang, Ying" <ying.huang@intel.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-kernel@vger.kernel.org, Zi Yan <ziy@nvidia.com>
Subject: [PATCH v3 0/3] Various memory tiering fixes
Date: Wed, 24 Jul 2024 09:01:12 -0400 [thread overview]
Message-ID: <20240724130115.793641-1-ziy@nvidia.com> (raw)
Changelog
===
From v2:
1. Renamed folio_has_cpupid() to folio_use_access_time() and reverse the
code logic, since folio_has_cpupid() = !folio_use_access_time().
2. Wrapped folio_use_access_time() with CONFIG_NUMA_BALANCING to avoid the
function redefinition compilation error.
From v1:
1. Added a memory tiering runtime check in migrate_misplaced_folio() to
correct PGPROMOTE_SUCCESS counting.
2. Moved folio_has_cpupid() from memory-tiers.h to mm.h.
From RFC:
1. Added Reported-by and Closes flags to first patch
Zi Yan (3):
memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page()
memory tiering: introduce folio_use_access_time() check
memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled.
include/linux/mm.h | 6 ++++++
kernel/sched/fair.c | 3 +--
mm/huge_memory.c | 5 ++---
mm/memory-tiers.c | 19 +++++++++++++++++++
mm/memory.c | 3 +--
mm/migrate.c | 4 +++-
mm/mprotect.c | 3 +--
7 files changed, 33 insertions(+), 10 deletions(-)
--
2.43.0
next reply other threads:[~2024-07-24 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 13:01 Zi Yan [this message]
2024-07-24 13:01 ` [PATCH v3 1/3] memory tiering: read last_cpupid correctly in do_huge_pmd_numa_page() Zi Yan
2024-07-24 13:01 ` [PATCH v3 2/3] memory tiering: introduce folio_use_access_time() check Zi Yan
2024-07-24 14:13 ` David Hildenbrand
2024-07-25 1:01 ` Kefeng Wang
2024-07-24 13:01 ` [PATCH v3 3/3] memory tiering: count PGPROMOTE_SUCCESS when mem tiering is enabled Zi Yan
2024-07-24 14:14 ` David Hildenbrand
2024-07-25 1:00 ` 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=20240724130115.793641-1-ziy@nvidia.com \
--to=ziy@nvidia.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=lorenzo.stoakes@oracle.com \
--cc=wangkefeng.wang@huawei.com \
--cc=ying.huang@intel.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