From: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>
To: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>
Cc: Yu Zhao <yuzhao@google.com>, Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages
Date: Fri, 17 Feb 2023 17:28:09 +0530 [thread overview]
Message-ID: <6bbf2c47-05ab-b78c-3165-2eff18962d6d@linux.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
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. 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.
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
[-- Attachment #2: mongodb-perf-lsf-mm.png --]
[-- Type: image/png, Size: 108289 bytes --]
next reply other threads:[~2023-02-17 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:58 Aneesh Kumar K V [this message]
2023-02-17 16:42 ` [LSF/MM/BPF TOPIC] Using hardware counters to determine hot/cold pages 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
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=6bbf2c47-05ab-b78c-3165-2eff18962d6d@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=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).