Re: [RFC][PATCH 1/2] memcg: Ensure every task that uses an mm is in the same memory cgroup
From: Michal Hocko
Date: Mon Jun 04 2018 - 09:01:28 EST
[dropping Kirill Tkhai from the CC because I get rejection from the mail
On Fri 01-06-18 12:16:52, Tejun Heo wrote:
> On Fri, Jun 01, 2018 at 01:11:59PM -0500, Eric W. Biederman wrote:
> > Widening the definition of a process sounds good. The memory control
> > group code would still need a way to forbid these in cgroup v1 mode,
> > when someone uses the task file.
> Yeap, you're right. We'll need memcg's can_attach rejecting for v1.
Do we really need? I mean, do we know about any existing usecase that
would need this weird threading concept and depend on memory migration
which doesn't really work?