From: Yuanchu Xie <yuanchu@google.com>
To: David Hildenbrand <david@redhat.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Khalid Aziz <khalid.aziz@oracle.com>,
Henry Huang <henry.hj@antgroup.com>, Yu Zhao <yuzhao@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Gregory Price <gregory.price@memverge.com>,
Huang Ying <ying.huang@intel.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Kalesh Singh <kaleshsingh@google.com>,
Wei Xu <weixugc@google.com>,
David Rientjes <rientjes@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Shuah Khan <shuah@kernel.org>,
Yosry Ahmed <yosryahmed@google.com>,
Matthew Wilcox <willy@infradead.org>,
Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>,
Kairui Song <kasong@tencent.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Vasily Averin <vasily.averin@linux.dev>,
Nhat Pham <nphamcs@gmail.com>, Miaohe Lin <linmiaohe@huawei.com>,
Qi Zheng <zhengqi.arch@bytedance.com>,
Abel Wu <wuyun.abel@bytedance.com>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Yuanchu Xie <yuanchu@google.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: [PATCH v2 1/8] mm: multi-gen LRU: ignore non-leaf pmd_young for force_scan=true
Date: Mon, 3 Jun 2024 19:05:42 -0700 [thread overview]
Message-ID: <20240604020549.1017540-2-yuanchu@google.com> (raw)
In-Reply-To: <20240604020549.1017540-1-yuanchu@google.com>
When non-leaf pmd accessed bits are available, MGLRU page table walks
can clear the non-leaf pmd accessed bit and ignore the accessed bit on
the pte if it's on a different node, skipping a generation update as
well. If another scan occurrs on the same node as said skipped pte.
the non-leaf pmd accessed bit might remain cleared and the pte accessed
bits won't be checked. While this is sufficient for reclaim-driven
aging, where the goal is to select a reasonably cold page, the access
can be missed when aging proactively for workingset estimation of a of a
node/memcg.
In more detail, get_pfn_folio returns NULL if the folio's nid != node
under scanning, so the page table walk skips processing of said pte. Now
the pmd_young flag on this pmd is cleared, and if none of the pte's are
accessed before another scan occurrs on the folio's node, the pmd_young
check fails and the pte accessed bit is skipped.
Since force_scan disables various other optimizations, we check
force_scan to ignore the non-leaf pmd accessed bit.
Signed-off-by: Yuanchu Xie <yuanchu@google.com>
---
mm/vmscan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index d55e8d07ffc4..73f3718b33f7 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -3548,7 +3548,7 @@ static void walk_pmd_range(pud_t *pud, unsigned long start, unsigned long end,
walk->mm_stats[MM_NONLEAF_TOTAL]++;
- if (should_clear_pmd_young()) {
+ if (!walk->force_scan && should_clear_pmd_young()) {
if (!pmd_young(val))
continue;
--
2.45.1.467.gbab1589fc0-goog
next prev parent reply other threads:[~2024-06-04 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 2:05 [PATCH v2 0/8] mm: workingset reporting Yuanchu Xie
2024-06-04 2:05 ` Yuanchu Xie [this message]
2024-06-04 3:56 ` [PATCH v2 1/8] mm: multi-gen LRU: ignore non-leaf pmd_young for force_scan=true Lance Yang
2024-07-10 17:59 ` Yu Zhao
2024-06-04 2:05 ` [PATCH v2 2/8] mm: aggregate working set information into histograms Yuanchu Xie
2024-06-04 2:05 ` [PATCH v2 3/8] mm: use refresh interval to rate-limit workingset report aggregation Yuanchu Xie
2024-06-04 2:05 ` [PATCH v2 4/8] mm: report workingset during memory pressure driven scanning Yuanchu Xie
2024-06-04 2:05 ` [PATCH v2 5/8] mm: extend working set reporting to memcgs Yuanchu Xie
2024-06-04 22:55 ` kernel test robot
2024-06-04 2:05 ` [PATCH v2 6/8] mm: add kernel aging thread for workingset reporting Yuanchu Xie
2024-06-04 2:05 ` [PATCH v2 7/8] selftest: test system-wide " Yuanchu Xie
2024-06-04 2:05 ` [PATCH v2 8/8] Docs/admin-guide/mm/workingset_report: document sysfs and memcg interfaces Yuanchu Xie
2024-06-06 17:02 ` Randy Dunlap
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=20240604020549.1017540-2-yuanchu@google.com \
--to=yuanchu@google.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=cgroups@vger.kernel.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.price@memverge.com \
--cc=hannes@cmpxchg.org \
--cc=henry.hj@antgroup.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=khalid.aziz@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=quic_sudaraja@quicinc.com \
--cc=rafael@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=vasily.averin@linux.dev \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=wuyun.abel@bytedance.com \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.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