Re: [PATCH v2 1/3] sched/numa: make free-space tiering promotion bypass configurable

["Li Zhe" <lizhe.67@bytedance.com>]

On 10/30/26 11:44 AM, Bharata B Rao wrote:
> 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.


Thanks, Bharata.

I would appreciate further maintainer feedback on whether this series
looks acceptable.

Thanks,
Zhe

>
> Regards,
> Bharata.