From: Bharata B Rao <bharata@amd.com>
To: Gregory Price <gourry@gourry.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<Jonathan.Cameron@huawei.com>, <dave.hansen@intel.com>,
<mgorman@techsingularity.net>, <mingo@redhat.com>,
<peterz@infradead.org>, <raghavendra.kt@amd.com>,
<riel@surriel.com>, <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@redhat.com>,
<byungchul@sk.com>, <kinseyho@google.com>,
<joshua.hahnjy@gmail.com>, <yuanchu@google.com>,
<balbirs@nvidia.com>, <alok.rathore@samsung.com>,
<shivankg@amd.com>
Subject: Re: [RFC PATCH v5 00/10] mm: Hot page tracking and promotion infrastructure
Date: Thu, 12 Feb 2026 07:46:34 +0530 [thread overview]
Message-ID: <0b03e16d-ca4a-4a70-b530-14bbe42bb7ad@amd.com> (raw)
In-Reply-To: <aYyomjsBpZ2KFxKG@gourry-fedora-PF4VCD3F>
On 11-Feb-26 9:34 PM, Gregory Price wrote:
> On Wed, Feb 11, 2026 at 09:00:26PM +0530, Bharata B Rao wrote:
>> =====================================================================================
>> Base Base pghot-default
>> pghot-precise
>> NUMAB0 NUMAB2 NUMAB2 NUMAB2
>> =====================================================================================
>> harmonic_mean_TEPS 5.10676e+08 7.56804e+08 5.92473e+08 7.47091e+08
>> mean_time 8.41027 5.67508 7.24915 5.74886
>> median_TEPS 5.11535e+08 7.24252e+08 5.63155e+08 7.71638e+08
>> max_TEPS 5.1785e+08 1.06051e+09 7.88018e+08 1.0504e+09
>>
>> pgpromote_success 0 13557718 13737730 13734469
>> numa_pte_updates 0 26491591 26848847 26726856
>> numa_hint_faults 0 13558077 13882743 13798024
>> =====================================================================================
>>
>
> Can you contextualize TEPS? Higher better? Higher worse? etc.
In the Graph500 benchmark, higher TEPS (Traversed Edges Per Second) values are
better.
Regards,
Bharata.
next prev parent reply other threads:[~2026-02-12 2:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 14:40 [RFC PATCH v5 00/10] mm: Hot page tracking and promotion infrastructure Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 01/10] mm: migrate: Allow misplaced migration without VMA Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 02/10] migrate: Add migrate_misplaced_folios_batch() Bharata B Rao
2026-02-26 20:40 ` Joshua Hahn
2026-02-27 14:41 ` Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 03/10] mm: Hot page tracking and promotion Bharata B Rao
2026-02-11 15:40 ` Bharata B Rao
2026-02-11 16:08 ` Gregory Price
2026-02-12 2:03 ` Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 04/10] mm: pghot: Precision mode for pghot Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 05/10] mm: sched: move NUMA balancing tiering promotion to pghot Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 06/10] x86: ibs: In-kernel IBS driver for memory access profiling Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 07/10] x86: ibs: Enable IBS profiling for memory accesses Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 08/10] mm: mglru: generalize page table walk Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 09/10] mm: klruscand: use mglru scanning for page promotion Bharata B Rao
2026-01-29 14:40 ` [RFC PATCH v5 10/10] mm: pghot: Add folio_mark_accessed() as hotness source Bharata B Rao
2026-02-09 3:25 ` [RFC PATCH v5 00/10] mm: Hot page tracking and promotion infrastructure Bharata B Rao
2026-02-09 3:30 ` Bharata B Rao
2026-02-11 15:30 ` Bharata B Rao
2026-02-11 16:04 ` Gregory Price
2026-02-12 2:16 ` Bharata B Rao [this message]
2026-02-11 16:06 ` Gregory Price
2026-02-12 16:15 ` Bharata B Rao
2026-02-13 14:56 ` Gregory Price
2026-02-16 3:00 ` Bharata B Rao
2026-02-23 14:27 ` Bharata B Rao
2026-02-23 15:02 ` Gregory Price
2026-02-24 11:55 ` Bharata B Rao
2026-02-24 15:30 ` Gregory Price
2026-02-25 4:35 ` 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=0b03e16d-ca4a-4a70-b530-14bbe42bb7ad@amd.com \
--to=bharata@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alok.rathore@samsung.com \
--cc=balbirs@nvidia.com \
--cc=byungchul@sk.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=shivankg@amd.com \
--cc=sj@kernel.org \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--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 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.