From: "Li Zhe" <lizhe.67@bytedance.com>
To: "Peter Zijlstra" <peterz@infradead.org>, <bharata@amd.com>
Cc: <akpm@linux-foundation.org>, <bsegall@google.com>,
<david@kernel.org>, <dietmar.eggemann@arm.com>,
<gourry@gourry.net>, <joshua.hahnjy@gmail.com>,
<juri.lelli@redhat.com>, <kprateek.nayak@amd.com>,
<ljs@kernel.org>, <mgorman@suse.de>, <mingo@redhat.com>,
<riel@redhat.com>, <rostedt@goodmis.org>,
<vincent.guittot@linaro.org>, <vschneid@redhat.com>,
<ziy@nvidia.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v2 0/3] sched/numa: refine memory tiering promotion heuristics
Date: Thu, 29 Oct 2026 10:49:03 +0800 [thread overview]
Message-ID: <b32b2bec-4fa1-4899-9014-52a6568cbd73@bytedance.com> (raw)
In-Reply-To: <20261028092004.GG2668804@noisy.programming.kicks-ass.net>
On 10/28/26 5:20 PM, Peter Zijlstra wrote:
> On Wed, Oct 28, 2026 at 12:12:50PM +0800, Li Zhe wrote:
>> This version narrows the series to memory tiering. The generic normal
>> NUMA balancing cleanups and heuristic changes from v1 are not included.
> Should we not look at Bharata's pghot stuff first and untangle this numa
> balancing vs tiering nonsense, before making an even bigger mess of
> things?
I agree that pghot is relevant to the longer-term direction. My
understanding is that the two ideas are not conflicting with each other:
this series tries to refine the current NUMA-balancing-based tiering
implementation, while pghot would be a larger rework of the promotion
infrastructure.
Let's also copy Bharata here so he is aware of this discussion.
Based on Joshua's comment, I can also split patch 2 out as a standalone
fix with a proper Fixes tag, and keep patches 1 and 3 for the broader
tiering heuristic discussion.
Thanks,
Zhe
prev parent reply other threads:[~2026-10-29 2:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 4:12 Li Zhe
2026-10-28 4:12 ` [PATCH v2 1/3] sched/numa: make free-space tiering promotion bypass configurable Li Zhe
2026-10-29 4:16 ` Bharata B Rao
2026-10-29 6:24 ` Li Zhe
2026-10-29 9:34 ` Bharata B Rao
2026-10-29 9:46 ` Li Zhe
2026-10-29 10:22 ` Bharata B Rao
2026-10-29 11:33 ` Li Zhe
2026-10-28 4:12 ` [PATCH v2 2/3] sched/numa: do not feed tiering promotions into task placement stats Li Zhe
2026-10-28 15:03 ` Joshua Hahn
2026-10-29 2:52 ` Li Zhe
2026-10-29 5:51 ` Bharata B Rao
2026-10-29 6:29 ` Li Zhe
2026-10-28 4:12 ` [PATCH v2 3/3] sched/numa: fix scan-period adjustment for tiering-only mode Li Zhe
2026-10-29 6:21 ` Bharata B Rao
2026-10-29 8:16 ` Li Zhe
2026-10-28 9:20 ` [PATCH v2 0/3] sched/numa: refine memory tiering promotion heuristics Peter Zijlstra
2026-10-29 2:49 ` Li Zhe [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=b32b2bec-4fa1-4899-9014-52a6568cbd73@bytedance.com \
--to=lizhe.67@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=bsegall@google.com \
--cc=david@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®