[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b816f58a-ce25-c079-c6b3-a3406df246f9@openvz.org>
Date: Thu, 11 Aug 2022 06:19:12 +0300
From: Vasily Averin <vvs@...nvz.org>
To: Tejun Heo <tj@...nel.org>,
Michal Koutný <mkoutny@...e.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-kernel@...r.kernel.org, kernel@...nvz.org,
Shakeel Butt <shakeelb@...gle.com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Muchun Song <songmuchun@...edance.com>,
Michal Hocko <mhocko@...e.com>,
Johannes Weiner <hannes@...xchg.org>
Subject: Re: [PATCH 0/3] enable memcg accounting for kernfs objects
On 8/9/22 20:56, Tejun Heo wrote:
> Hello,
>
> On Tue, Aug 09, 2022 at 07:49:34PM +0200, Michal Koutný wrote:
>> On Tue, Aug 09, 2022 at 07:31:31AM -1000, Tejun Heo <tj@...nel.org> wrote:
>>> I'm not quite sure whether following the usual "charge it to the allocating
>>> task's cgroup" is the best way to go about it. I wonder whether it'd be
>>> better to attach it to the new cgroup's nearest ancestor with memcg enabled.
>>
>> See also
>> https://lore.kernel.org/r/YnBLge4ZQNbbxufc@blackbook/
>> and
>> https://lore.kernel.org/r/20220511163439.GD24172@blackbody.suse.cz/
>
> Ah, thanks. Vasily, can you please include some summary of the discussions
> and the rationales for the path taken in the commit message?
Dear Tejun,
thank you for the feedback, I'll do it in next patch set iteration.
However, I noticed another problem in neighborhood and I planned to
add new patches into current patch set. One of the new patches is quite simple,
however second one is quite complex and requires some discussion.
So I'm still thinking how best to solve these issues.
Thank you,
Vasily Averin
Powered by blists - more mailing lists