[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250617223005.2526-1-sj@kernel.org>
Date: Tue, 17 Jun 2025 15:30:05 -0700
From: SeongJae Park <sj@...nel.org>
To: Bijan Tabatabai <bijan311@...il.com>
Cc: SeongJae Park <sj@...nel.org>,
Gregory Price <gourry@...rry.net>,
David Hildenbrand <david@...hat.com>,
linux-mm@...ck.org,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org,
corbet@....net,
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,
damon@...ts.linux.dev
Subject: Re: [RFC PATCH 1/4] mm/mempolicy: Expose policy_nodemask() in include/linux/mempolicy.h
On Tue, 17 Jun 2025 14:54:39 -0500 Bijan Tabatabai <bijan311@...il.com> wrote:
[...]
> Given this discussion, as well as Joshua's comments earlier [1], it
> sounds like while people aren't exactly opposed to using mempolicy for
> this, the building consensus is that it would be best not to. I will
> move the interleave logic to DAMON for the next revision. However, I
> still think it makes sense to use the global weights (probably via
> get_il_weight) for now to avoid allocating pages a certain way and
> then migrating them soon after.
Makes sense to me :)
>
> I'll try to send the next version of the patch set by the end of the week.
Looking forwrd to it!
Thanks,
SJ
[...]
Powered by blists - more mailing lists