From: Michal Hocko <mhocko@suse.com>
To: Zhou Guanghui <zhouguanghui1@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, wangkefeng.wang@huawei.com,
guohanjun@huawei.com, dingtianhong@huawei.com,
chenweilong@huawei.com, rui.xiang@huawei.com,
Johannes Weiner <hannes@cmpxchg.org>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] mm/memcg: set memcg when split pages
Date: Tue, 2 Mar 2021 16:51:05 +0100 [thread overview]
Message-ID: <YD5e2k0ecvGt8sqR@dhcp22.suse.cz> (raw)
In-Reply-To: <YD4CciUX0/eXFLM0@dhcp22.suse.cz>
On Tue 02-03-21 10:17:03, Michal Hocko wrote:
> [Cc Johannes for awareness and fixup Nick's email]
>
> On Tue 02-03-21 01:34:51, Zhou Guanghui wrote:
> > When split page, the memory cgroup info recorded in first page is
> > not copied to tail pages. In this case, when the tail pages are
> > freed, the uncharge operation is not performed. As a result, the
> > usage of this memcg keeps increasing, and the OOM may occur.
> >
> > So, the copying of first page's memory cgroup info to tail pages
> > is needed when split page.
>
> I was not aware that alloc_pages_exact is used for accounted allocations
> but git grep told me otherwise so this is not a theoretical one. Both
> users (arm64 and s390 kvm) are quite recent AFAICS. split_page is also
> used in dma allocator but I got lost in indirection so I have no idea
> whether there are any users there.
>
> The page itself looks reasonable to me.
>
> > Signed-off-by: Zhou Guanghui <zhouguanghui1@huawei.com>
>
> Acked-by: Michal Hocko <mhocko@suse.com>
>
> Minor nit
>
> > ---
> > include/linux/memcontrol.h | 10 ++++++++++
> > mm/page_alloc.c | 4 +++-
> > 2 files changed, 13 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> > index e6dc793d587d..c7e2b4421dc1 100644
> > --- a/include/linux/memcontrol.h
> > +++ b/include/linux/memcontrol.h
> > @@ -867,6 +867,12 @@ void mem_cgroup_print_oom_group(struct mem_cgroup *memcg);
> > extern bool cgroup_memory_noswap;
> > #endif
> >
> > +static inline void copy_page_memcg(struct page *dst, struct page *src)
> > +{
> > + if (src->memcg_data)
> > + dst->memcg_data = src->memcg_data;
>
> I would just drop the test. The struct page is a single cache line which
> is dirty by the reference count so another store will unlikely be
> noticeable even when NULL is stored here and you safe a conditional.
Disregard this. As Zi Yan mentioned in other reply, we need to keep the
check and take a css reference along with transfering the memcg.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-03-02 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 1:34 [PATCH] mm/memcg: set memcg when split pages Zhou Guanghui
2021-03-02 1:59 ` Zi Yan
2021-03-02 7:05 ` Zhouguanghui (OS Kernel)
2021-03-02 15:37 ` Zi Yan
2021-03-02 15:42 ` Michal Hocko
2021-03-02 9:17 ` Michal Hocko
2021-03-02 15:51 ` Michal Hocko [this message]
2021-03-02 20:24 ` Hugh Dickins
2021-03-02 22:56 ` Johannes Weiner
2021-03-02 23:49 ` Hugh Dickins
2021-03-03 7:46 ` Michal Hocko
2021-03-03 9:15 ` Zhouguanghui (OS Kernel)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YD5e2k0ecvGt8sqR@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=chenweilong@huawei.com \
--cc=dingtianhong@huawei.com \
--cc=guohanjun@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=rui.xiang@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=zhouguanghui1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).