mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@amd.com>
To: Li Zhe <lizhe.67@bytedance.com>, <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>, <peterz@infradead.org>, <rostedt@goodmis.org>,
	<vincent.guittot@linaro.org>, <vschneid@redhat.com>,
	<ziy@nvidia.com>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>
Subject: Re: [PATCH v2 1/3] sched/numa: make free-space tiering promotion bypass configurable
Date: Fri, 30 Oct 2026 09:14:57 +0530	[thread overview]
Message-ID: <c9cf96bf-f3b1-47da-b22a-9600b5fb01be@amd.com> (raw)
In-Reply-To: <1bab234e-8914-4694-b0aa-f265fa49c6d3@bytedance.com>

On 29-Oct-26 5:03 PM, Li Zhe wrote:
> Yes, the case I am trying to cover is closer to the non-overcommitted
> case.  We do have deployments where memory is intentionally placed across
> DRAM and CXL memory, instead of relying only on natural spillover from a
> full top tier.
> 
> For example, the orchestration layer may want a cgroup to use a planned
> DRAM/CXL ratio, so that DRAM capacity remains available for later
> placement decisions or other workloads.
> 
> In such setups, the top tier can still have free space, but we may not
> want short cold accesses to refill it simply because the free-space
> bypass is available.  The intent of this patch is to let those
> deployments keep using the existing hotness and rate-limit checks even
> when there is top-tier headroom.

Thanks for this information about the deployment model. This is a useful
conclusion to reach.

Regards,
Bharata.

  reply	other threads:[~2026-10-30  3:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28  4:12 [PATCH v2 0/3] sched/numa: refine memory tiering promotion heuristics 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-30  3:44           ` Bharata B Rao [this message]
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

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=c9cf96bf-f3b1-47da-b22a-9600b5fb01be@amd.com \
    --to=bharata@amd.com \
    --cc=akpm@linux-foundation.org \
    --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=lizhe.67@bytedance.com \
    --cc=ljs@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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®