[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aNEG5W0qLPKKflQA@tiehlicka>
Date: Mon, 22 Sep 2025 10:20:53 +0200
From: Michal Hocko <mhocko@...e.com>
To: xu.xin16@....com.cn
Cc: akpm@...ux-foundation.org, shakeel.butt@...ux.dev, hannes@...xchg.org,
roman.gushchin@...ux.dev, david@...hat.com,
chengming.zhou@...ux.dev, muchun.song@...ux.dev,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
cgroups@...r.kernel.org
Subject: Re: [PATCH linux-next v3 0/6] memcg: Support per-memcg KSM metrics
On Sun 21-09-25 23:07:26, xu.xin16@....com.cn wrote:
> From: xu xin <xu.xin16@....com.cn>
>
> v2->v3:
> ------
> Some fixes of compilation error due to missed inclusion of header or missed
> function definition on some kernel config.
> https://lore.kernel.org/all/202509142147.WQI0impC-lkp@intel.com/
> https://lore.kernel.org/all/202509142046.QatEaTQV-lkp@intel.com/
>
> v1->v2:
> ------
> According to Shakeel's suggestion, expose these metric item into memory.stat
> instead of a new interface.
> https://lore.kernel.org/all/ir2s6sqi6hrbz7ghmfngbif6fbgmswhqdljlntesurfl2xvmmv@yp3w2lqyipb5/
>
> Background
> ==========
>
> With the enablement of container-level KSM (e.g., via prctl [1]), there is
> a growing demand for container-level observability of KSM behavior. However,
> current cgroup implementations lack support for exposing KSM-related metrics.
Could you be more specific why this is needed and what it will be used
for?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists