Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211220085649.8196-1-songmuchun@bytedance.com>
 <20211220085649.8196-11-songmuchun@bytedance.com> <20220106110051.GA470@blackbody.suse.cz>
 <CAMZfGtXZA+rLMUw5yLSW=eUncT0BjH++Dpi1EzKwXvV9zwqF1w@mail.gmail.com> <20220113133213.GA28468@blackbody.suse.cz>
In-Reply-To: <20220113133213.GA28468@blackbody.suse.cz>
From:   Muchun Song <songmuchun@bytedance.com>
Date:   Tue, 18 Jan 2022 20:05:44 +0800
Message-ID: <CAMZfGtWJeov9XD_MEkDJwTK5b73OKPYxJBQi=D5-NSyNSSKLCw@mail.gmail.com>
Subject: Re: [PATCH v5 10/16] mm: list_lru: allocate list_lru_one only when needed
To:     =?UTF-8?Q?Michal_Koutn=C3=BD?= <mkoutny@suse.com>
Cc:     Matthew Wilcox <willy@infradead.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Michal Hocko <mhocko@kernel.org>,
        Vladimir Davydov <vdavydov.dev@gmail.com>,
        Shakeel Butt <shakeelb@google.com>,
        Roman Gushchin <guro@fb.com>, Yang Shi <shy828301@gmail.com>,
        Alex Shi <alexs@kernel.org>,
        Wei Yang <richard.weiyang@gmail.com>,
        Dave Chinner <david@fromorbit.com>,
        trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
        jaegeuk@kernel.org, chao@kernel.org,
        Kari Argillander <kari.argillander@gmail.com>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux Memory Management List <linux-mm@kvack.org>,
        linux-nfs@vger.kernel.org, Qi Zheng <zhengqi.arch@bytedance.com>,
        Xiongchun duan <duanxiongchun@bytedance.com>,
        Fam Zheng <fam.zheng@bytedance.com>,
        Muchun Song <smuchun@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, Jan 13, 2022 at 9:32 PM Michal Koutn=C3=BD <mkoutny@suse.com> wrote=
:
>
> On Wed, Jan 12, 2022 at 09:22:36PM +0800, Muchun Song <songmuchun@bytedan=
ce.com> wrote:
> >   root(-1) -> A(0) -> B(1) -> C(2)
> >
> > CPU0:                                   CPU1:
> > memcg_list_lru_alloc(C)
> >                                         memcg_drain_all_list_lrus(C)
> >                                         memcg_drain_all_list_lrus(B)
> >                                         // Now C and B are offline. The
> >                                         // kmemcg_id becomes the follow=
ing if
> >                                         // we do not the kmemcg_id of i=
ts
> >                                         // descendants in
> >                                         // memcg_drain_all_list_lrus().
> >                                         //
> >                                         // root(-1) -> A(0) -> B(0) -> =
C(1)
> >
> >   for (i =3D 0; memcg; memcg =3D parent_mem_cgroup(memcg), i++) {
> >       // allocate struct list_lru_per_memcg for memcg C
> >       table[i].mlru =3D memcg_init_list_lru_one(gfp);
> >   }
> >
> >   spin_lock_irqsave(&lru->lock, flags);
> >   while (i--) {
> >       // here index =3D 1
> >       int index =3D table[i].memcg->kmemcg_id;
> >
> >       struct list_lru_per_memcg *mlru =3D table[i].mlru;
> >       if (index < 0 || rcu_dereference_protected(mlrus->mlru[index], tr=
ue))
> >           kfree(mlru);
> >       else
> >           // mlrus->mlru[index] will be assigned a new value regardless
> >           // memcg C is already offline.
> >           rcu_assign_pointer(mlrus->mlru[index], mlru);
> >   }
> >   spin_unlock_irqrestore(&lru->lock, flags);
> >
>
> > So changing ->kmemcg_id of all its descendants can prevent
> > memcg_list_lru_alloc() from allocating list lrus for the offlined
> > cgroup after memcg_list_lru_free() calling.
>
> Thanks for the illustrative example. I can see how this can be a problem
> in a general call of memcg_list_lru_alloc(C).
>
> However, the code, as I understand it, resolves the memcg to which lru
> allocation should be associated via get_mem_cgroup_from_objcg() and
> memcg_reparent_list_lrus(C) comes after memcg_reparent_objcgs(C, B),
> i.e. the allocation would target B (or even A if after
> memcg_reparent_objcgs(B, A))?
>
> It seems to me like "wasting" the existing objcg reparenting mechanism.
> Or what do you think could be a problem relying on it?
>

I have thought about this. It's a little different to rely on objcg
reparenting since the user can get memcg from objcg and
then does not realize the memcg has reparented. Although it
can check memcg->objcg to know whether the memcg is
reparented, it should also prevent this memcg from being
reparented throughout memcg_list_lru_alloc(). Maybe
holding css_set_lock can do that. I do not think this
is a good choice. Do you have any thoughts about this?

Thanks.