[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aF2b160mlNozbP4o@gourry-fedora-PF4VCD3F>
Date: Thu, 26 Jun 2025 14:13:27 -0500
From: Gregory Price <gourry@...rry.net>
To: Bijan Tabatabai <bijan311@...il.com>
Cc: SeongJae Park <sj@...nel.org>, damon@...ts.linux.dev,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, david@...hat.com, ziy@...dia.com,
matthew.brost@...el.com, joshua.hahnjy@...il.com, rakie.kim@...com,
byungchul@...com, ying.huang@...ux.alibaba.com, apopple@...dia.com,
bijantabatab@...ron.com, venkataravis@...ron.com,
emirakhur@...ron.com, ajayjoshi@...ron.com, vtavarespetr@...ron.com
Subject: Re: [RFC PATCH v2 0/2] mm/damon/paddr: Allow interleaving in
migrate_{hot,cold} actions
On Mon, Jun 23, 2025 at 06:21:20PM -0500, Bijan Tabatabai wrote:
> I'm not convinced this is true. If you have a workload that can
> saturate the local bandwidth but not the remote bandwidth, wouldn't
> you want the interleave weights to be more biased towards local memory
> than you would for a workload that can saturate both the local and
> remote bandwidth?
>
That sounds like an argument for task/process/cgroup-local weights, as
opposed to an argument to twiddle global weights.
These things need not solve all problems for everyone.
~Gregory
Powered by blists - more mailing lists