From: Bharata B Rao <bharata@amd.com>
To: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <tglx@kernel.org>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<xin@zytor.com>, <luto@kernel.org>, <peterz@infradead.org>,
<Jonathan.Cameron@huawei.com>, <gourry@gourry.net>,
<rientjes@google.com>, <sj@kernel.org>, <weixugc@google.com>,
<willy@infradead.org>, <ying.huang@linux.alibaba.com>,
<ziy@nvidia.com>, <dave@stgolabs.net>, <nifan.cxl@gmail.com>,
<xuezhengchu@huawei.com>, <yiannis@zptcorp.com>,
<akpm@linux-foundation.org>, <david@kernel.org>,
<byungchul@sk.com>, <kinseyho@google.com>,
<joshua.hahnjy@gmail.com>, <yuanchu@google.com>,
<balbirs@nvidia.com>, <shivankg@amd.com>,
<donettom@linux.ibm.com>, <linyongting@bytedance.com>
Subject: Re: [RFC PATCH v0 0/3] pghot: x86: IBS Memory Profiler for hot page promotion
Date: Thu, 24 Sep 2026 11:57:46 +0530 [thread overview]
Message-ID: <5e3b81d0-c086-45e1-a682-a4a68253189e@amd.com> (raw)
In-Reply-To: <20260924062206.319314-1-bharata@amd.com>
On 24-Sep-26 11:52 AM, Bharata B Rao wrote:
>
> Detailed per-benchmark tables (throughput/latency + vmstat and pghot
> promotion counters) are posted as replies to this thread.
Graph500 tiering comparison: base vs pghot (hwhints)
====================================================
Kernel(s) : base = 7.3.0-rc2-base+
pghot = 7.3.0-rc2-pghot+
Benchmark : Graph500 reference BFS, SCALE=28, edgefactor=16, 128 ranks
Topology : top-tier NUMA node=1 (CPUs+DRAM), lower-tier node=2 (mem-only/CXL)
Note : SKIP_VALIDATION=1 (timing-only); all TEPS carry Graph500 (!) flag.
Figure of merit is harmonic_mean_TEPS (hmean).
Config legend
-------------
C1 : base kernel, no tiering (numa_balancing=0)
C2 : base kernel, NUMAB2 tiering (numa_balancing=2)
C3 : pghot kernel, hwhints source (pghot_enabled_sources=2,
pghot_freq_threshold=1, pghot_target_nid=0 [default],
IBS mem-profiler on, numa_balancing=0, promotion=off)
Column legend
-------------
hmean : harmonic_mean_TEPS (primary Graph500 metric)
hstddev : harmonic_stddev_TEPS
median : median_TEPS
bfs_t : mean BFS time (seconds)
spdup : speedup of hmean vs C1 baseline
Table 1: Performance
--------------------
+--------+------------+----------+------------+---------+--------+
| Config | hmean | hstddev | median | bfs_t | spdup |
| | (TEPS) | (TEPS) | (TEPS) | (sec) | |
+--------+------------+----------+------------+---------+--------+
| C1 | 5.543e+08 | 5.51e+05 | 5.548e+08 | 7.748 | 1.00x |
| C2 | 1.298e+09 | 6.80e+07 | 1.394e+09 | 3.308 | 2.34x |
| C3 | 1.755e+09 | 2.32e+07 | 1.805e+09 | 2.447 | 3.17x |
+--------+------------+----------+------------+---------+--------+
Table 2: Relevant kernel counters (/proc/vmstat deltas over the run)
--------------------------------------------------------------------
Values are accumulated deltas (before -> after) for the whole run.
+----------------------------+-----------+-----------+-----------+
| Counter | C1 | C2 | C3 |
+----------------------------+-----------+-----------+-----------+
| numa_pte_updates | 0 | 25867526 | 0 |
| numa_hint_faults | 0 | 13318442 | 0 |
| numa_pages_migrated | 0 | 13318248 | 3702779 |
| pgpromote_success | 0 | 13317996 | 3702779 |
| pghot_recorded_accesses | 0 | 0 | 3709015 |
| pghot_reported_hintfaults | 0 | 0 | 0 |
| pghot_reported_hwhints | 0 | 0 | 21385228 |
| hwhint_total_events | 0 | 0 | 21385281 |
| hwhint_dram_accesses | 0 | 0 | 16747814 |
| hwhint_extmem_accesses | 0 | 0 | 3697760 |
| hwhint_cache_accesses | 0 | 0 | 0 |
| hwhint_useful_events | 0 | 0 | 21385228 |
| hwhint_dropped_events | 0 | 0 | 0 |
| pgmigrate_success | 26841377 | 40161043 | 30548434 |
+----------------------------+-----------+-----------+-----------+
Key findings
------------
1. Tiering is the dominant win: C2 (base NUMAB2) reaches 2.34x and C3
(pghot hwhints) 3.17x over the untiered baseline (C1), where the
working set is stranded on the lower-tier/CXL node 2.
2. pghot hwhints now clearly leads base NUMAB2 on the official metric:
C3 1.755e9 (3.17x) vs C2 1.298e9 (2.34x) -> ~+35% hmean_TEPS.
3. hwhints/IBS is far more efficient and stable. C3 reaches its higher
hmean while:
- promoting only ~3.70M pages, ~1/4 of C2 (13.32M);
- issuing zero NUMA hint faults / PTE scans (numa_pte_updates=0);
- being ~3x more consistent (hstddev 2.32e7 vs 6.80e7).
IBS reported 21.39M hwhint events (16.75M DRAM + 3.70M ext-mem),
with hwhint_dropped_events=0.
4. median vs harmonic-mean: C2 median (1.394e9) sits well above its
hmean (1.298e9), reflecting high per-BFS variance in the fault-driven
path. C3 median (1.805e9) and hmean (1.755e9) sit close together ->
low variance.
Caveats
-------
* Single run per configuration; the median-vs-hmean spread for C2
indicates non-trivial run-to-run variance. Repeat runs are advisable
before drawing firm quantitative conclusions.
* SKIP_VALIDATION=1 was used (timing-only), so TEPS values are flagged
invalid (!) by Graph500 and are intended for relative comparison only.
next prev parent reply other threads:[~2026-09-24 6:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 6:22 Bharata B Rao
2026-09-24 6:22 ` [RFC PATCH v0 1/3] x86/ibs: Move IBS caps definitions into its own header Bharata B Rao
2026-09-24 6:22 ` [RFC PATCH v0 2/3] x86/mm/ibs: In-kernel driver for AMD IBS Memory Profiler Bharata B Rao
2026-09-24 6:22 ` [RFC PATCH v0 3/3] x86/mm/ibs: Add runtime controls for IBS memprofiler Bharata B Rao
2026-09-24 6:26 ` [RFC PATCH v0 0/3] pghot: x86: IBS Memory Profiler for hot page promotion Bharata B Rao
2026-09-24 6:27 ` Bharata B Rao [this message]
2026-09-24 6:31 ` Bharata B Rao
2026-09-24 6:33 ` Bharata B Rao
2026-09-24 6:35 ` Bharata B Rao
2026-09-24 6:37 ` 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=5e3b81d0-c086-45e1-a682-a4a68253189e@amd.com \
--to=bharata@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=bp@alien8.de \
--cc=byungchul@sk.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=david@kernel.org \
--cc=donettom@linux.ibm.com \
--cc=gourry@gourry.net \
--cc=hpa@zytor.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyongting@bytedance.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=shivankg@amd.com \
--cc=sj@kernel.org \
--cc=tglx@kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
--cc=xuezhengchu@huawei.com \
--cc=yiannis@zptcorp.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.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
all inboxes | Powered by JetHome®