From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Yang Shi <shy828301@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Yu Zhao <yuzhao@google.com>, Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages
Date: Sun, 19 Feb 2023 20:15:39 +0530 [thread overview]
Message-ID: <87a619g1d8.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAHbLzkrpV61m6-qwWrPheK-VXhsjEobPBWeuMYs6wkFPHPoa2A@mail.gmail.com>
Yang Shi <shy828301@gmail.com> writes:
> On Fri, Feb 17, 2023 at 3:58 AM Aneesh Kumar K V
> <aneesh.kumar@linux.ibm.com> wrote:
>>
>> PowerPC architecture (POWER10) supports a Hot/Cold page tracking
>> facility that provides access counter and access affinity details at
>> configurable page size granularity [1]. I have been looking at using
>> this counter in different areas of the kernel such as
>>
>> 1) Page reclaim/demotion
>> 2) THP utilization
>> 3) Page promotion.
>
> Not sure whether you are aware of this patchset:
> https://lore.kernel.org/linux-mm/20230208073533.715-1-bharata@amd.com/
>
> ARM64 has SPE which provides similar functionality. So I hope a common
> framework could be provided to hide the hardware details.
I will look at this discussion and see if there are some details I can reuse.
-aneesh
prev parent reply other threads:[~2023-02-19 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:58 [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages Aneesh Kumar K V
2023-02-17 16:42 ` SeongJae Park
2023-02-19 14:29 ` Aneesh Kumar K.V
2023-02-19 20:31 ` SeongJae Park
2023-02-17 16:53 ` Matthew Wilcox
2023-02-19 14:43 ` Aneesh Kumar K.V
2023-02-17 22:00 ` Yang Shi
2023-02-19 14:45 ` Aneesh Kumar K.V [this message]
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=87a619g1d8.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=shy828301@gmail.com \
--cc=yuzhao@google.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;
as well as URLs for NNTP newsgroup(s).