From: Matthew Wilcox <willy@infradead.org>
To: Bharata B Rao <bharata@amd.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Raghavendra K T <raghavendra.kt@amd.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
lsf-pc@lists.linux-foundation.org, gourry@gourry.net,
nehagholkar@meta.com, abhishekd@meta.com,
ying.huang@linux.alibaba.com, nphamcs@gmail.com,
hannes@cmpxchg.org, feng.tang@intel.com, kbusch@meta.com,
Hasan.Maruf@amd.com, sj@kernel.org, david@redhat.com,
k.shutemov@gmail.com, mgorman@techsingularity.net,
vbabka@suse.cz, hughd@google.com, rientjes@google.com,
shy828301@gmail.com, liam.howlett@oracle.com,
peterz@infradead.org, mingo@redhat.com, nadav.amit@gmail.com,
shivankg@amd.com, ziy@nvidia.com, jhubbard@nvidia.com,
AneeshKumar.KizhakeVeetil@arm.com, linux-kernel@vger.kernel.org,
jon.grimm@amd.com, santosh.shukla@amd.com, Michael.Day@amd.com,
riel@surriel.com, weixugc@google.com, leesuyeon0506@gmail.com,
honggyu.kim@sk.com, leillc@google.com, kmanaouil.dev@gmail.com,
rppt@kernel.org, dave.hansen@intel.com
Subject: Re: [LSF/MM/BPF TOPIC] Unifying sources of page temperature information - what info is actually wanted?
Date: Fri, 7 Feb 2025 09:50:55 +0000 [thread overview]
Message-ID: <Z6XXf5OaLe9ZaN02@casper.infradead.org> (raw)
In-Reply-To: <de31971e-98fc-4baf-8f4f-09d153902e2e@amd.com>
On Wed, Feb 05, 2025 at 11:54:05AM +0530, Bharata B Rao wrote:
> Here is a compilation of available temperature sources and how the
> hot/access data is consumed by different subsystems:
>
> PA-Physical address available
> VA-Virtual address available
> AA-Access time available
> NA-accessing Node info available
>
> I have left the slot blank for those which I am not sure about.
> ==================================================
> Temperature PA VA AA NA
> source
> ==================================================
> PROT_NONE faults Y Y Y Y
> --------------------------------------------------
> folio_mark_accessed() Y Y Y
> --------------------------------------------------
> PTE A bit Y Y N N
> --------------------------------------------------
> Platform hints Y Y Y Y
> (AMD IBS)
> --------------------------------------------------
> Device hints Y
> (CXL HMU)
> ==================================================
>
> And here is an attempt to compile how different subsystems
> use the above data:
> ==============================================================
> Source Subsystem Consumption
> ==============================================================
> PROT_NONE faults NUMAB NUMAB=1 locality based
> via process pgtable balancing
> walk NUMAB=2 hot page
> promotion
> ==============================================================
> folio_mark_accessed() FS/filemap/GUP LRU list activation
> ==============================================================
> PTE A bit via Reclaim:LRU LRU list activation,
> rmap walk deactivation/demotion
> ==============================================================
> PTE A bit via Reclaim:MGLRU LRU list activation,
> rmap walk and process deactivation/demotion
> pgtable walk
> ==============================================================
> PTE A bit via DAMON LRU activation,
> rmap walk hot page promotion,
> demotion etc
> ==============================================================
> Platform hints NUMAB NUMAB=1 Locality based
> (AMD IBS) balancing and
> NUMAB=2 hot page
> promotion
> ==============================================================
> Device hints NUMAB NUMAB=2 hot page
> promotion
> ==============================================================
> The last two are listed as possibilities.
>
> Feel free to correct/clarify and add more.
There's PG_young / PG_idle as well.
next prev parent reply other threads:[~2025-02-07 9:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:57 [LSF/MM/BPF TOPIC] Overhauling hot page detection and promotion based on PTE A bit scanning Raghavendra K T
2025-01-23 18:20 ` SeongJae Park
2025-01-24 8:54 ` Raghavendra K T
2025-01-24 18:05 ` Jonathan Cameron
2025-01-24 5:53 ` Hyeonggon Yoo
2025-01-24 9:02 ` Raghavendra K T
2025-01-27 7:01 ` David Rientjes
2025-01-27 7:11 ` Raghavendra K T
2025-02-06 3:14 ` Yuanchu Xie
2025-01-26 2:27 ` Huang, Ying
2025-01-27 5:11 ` Bharata B Rao
2025-01-27 18:34 ` SeongJae Park
2025-02-07 8:10 ` Huang, Ying
2025-02-07 9:06 ` Gregory Price
2025-02-07 19:52 ` SeongJae Park
2025-02-07 19:06 ` Davidlohr Bueso
2025-03-14 1:56 ` Raghavendra K T
2025-03-14 2:12 ` Raghavendra K T
2025-01-31 12:28 ` Jonathan Cameron
2025-01-31 13:09 ` [LSF/MM/BPF TOPIC] Unifying sources of page temperature information - what info is actually wanted? Jonathan Cameron
2025-02-05 6:24 ` Bharata B Rao
2025-02-05 16:05 ` Johannes Weiner
2025-02-06 6:46 ` SeongJae Park
2025-02-06 15:30 ` Jonathan Cameron
2025-02-07 9:50 ` Matthew Wilcox [this message]
2025-02-16 7:04 ` Huang, Ying
2025-02-16 6:49 ` Huang, Ying
2025-02-17 4:10 ` Bharata B Rao
2025-02-17 8:06 ` Huang, Ying
2025-03-14 14:24 ` Jonathan Cameron
2025-03-17 22:34 ` Davidlohr Bueso
2025-02-03 2:23 ` [LSF/MM/BPF TOPIC] Overhauling hot page detection and promotion based on PTE A bit scanning Raghavendra K T
2025-04-07 3:13 ` Bharata B Rao
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=Z6XXf5OaLe9ZaN02@casper.infradead.org \
--to=willy@infradead.org \
--cc=AneeshKumar.KizhakeVeetil@arm.com \
--cc=Hasan.Maruf@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Day@amd.com \
--cc=abhishekd@meta.com \
--cc=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=feng.tang@intel.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=honggyu.kim@sk.com \
--cc=hughd@google.com \
--cc=jhubbard@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=k.shutemov@gmail.com \
--cc=kbusch@meta.com \
--cc=kmanaouil.dev@gmail.com \
--cc=leesuyeon0506@gmail.com \
--cc=leillc@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=nehagholkar@meta.com \
--cc=nphamcs@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=santosh.shukla@amd.com \
--cc=shivankg@amd.com \
--cc=shy828301@gmail.com \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=ying.huang@linux.alibaba.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