[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZUyuL9_8PPiEflnS@tiehlicka>
Date: Thu, 9 Nov 2023 11:02:23 +0100
From: Michal Hocko <mhocko@...e.com>
To: Gregory Price <gourry.memverge@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-cxl@...r.kernel.org,
linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-doc@...r.kernel.org, ying.huang@...el.com,
akpm@...ux-foundation.org, tj@...nel.org, lizefan.x@...edance.com,
hannes@...xchg.org, corbet@....net, roman.gushchin@...ux.dev,
shakeelb@...gle.com, muchun.song@...ux.dev,
Gregory Price <gregory.price@...verge.com>
Subject: Re: [RFC PATCH v4 0/3] memcg weighted interleave mempolicy control
On Wed 08-11-23 19:25:14, Gregory Price wrote:
> This patchset implements weighted interleave and adds a new cgroup
> sysfs entry: cgroup/memory.interleave_weights (excluded from root).
Why have you chosen memory controler rather than cpuset controller?
TBH I do not think memcg is the best fit because traditionally memcg
accounts consumption rather than memory placement. This means that the
memory is already allocated when it is charged for a memcg. On the other
hand cpuset controller is the one to control the allocation placement so
it would seem a better fit.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists