From: SeongJae Park <sj@kernel.org>
To: Aneesh Kumar K V <aneesh.kumar@linux.ibm.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>,
damon@lists.linux.dev
Subject: Re: [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages
Date: Fri, 17 Feb 2023 16:42:11 +0000 [thread overview]
Message-ID: <20230217164211.59619-1-sj@kernel.org> (raw)
In-Reply-To: <6bbf2c47-05ab-b78c-3165-2eff18962d6d@linux.ibm.com>
Hi Aneesh,
On Fri, 17 Feb 2023 17:28:09 +0530 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.
>
> I have done some MGLRU integration and would like to discuss the
> observation with the rest of the community. It is still not clear what
> are the best ways to integrate these hardware counters in the Linux
> kernel.
Sounds very interesting. I think DAMON might be one another option, because it
is designed to be easy to extended with various source of access
information[1], and provides an abstraction layer for access temparature based
memory management[2], namely Data Access Monitoring-based Operation Schemes
(DAMOS).
> Attached is the performance graph showing how the mongodb/ycsb
> benchmark performs when using hardware counters with MGLRU aging. An
> early RFC version of the code can be found at
> https://github.com/kvaneesh/linux/commit/b472e2c8080823bb4114c286270aea3e18ffe221
> . I also expect we can get some numbers w.r.t THP usage before the
> conference.
I also have experimented a DAMON-based THP optimization[3], which shown
interesting results.
Hope to discuss about this with you at LSF/MM. FYI, I also proposed an LSF/MM
topic for DAMON[4].
[1] https://docs.kernel.org/mm/damon/design.html#configurable-layers
[2] https://docs.kernel.org/mm/damon/api.html#c.damos
[3] https://www.amazon.science/publications/daos-data-access-aware-operating-system
[4] https://lore.kernel.org/damon/20230214003328.55285-1-sj@kernel.org/
Thanks,
SJ
>
>
> X axis is the amount of memory that I am removing from the system so
> that I can force more memory reclaims. The total memory available is
> 50GB/single NUMA node/64 CPUs,40GB database with 40GB cache
> configuration.
>
>
> [1]
> https://hc32.hotchips.org/assets/program/conference/day1/HotChips2020_Server_Processors_IBM_Starke_POWER10_v33.pdf
>
next prev parent reply other threads:[~2023-02-17 16:42 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 [this message]
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
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=20230217164211.59619-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=damon@lists.linux.dev \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.