From: Haifeng Xu <haifeng.xu@shopee.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: akpm@linux-foundation.org, roman.gushchin@linux.dev,
songmuchun@bytedance.com, hannes@cmpxchg.org, vbabka@suse.cz,
willy@infradead.org, vasily.averin@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memcontrol: Skip root memcg in memcg_memory_event_mm
Date: Fri, 16 Dec 2022 09:43:02 +0800 [thread overview]
Message-ID: <abec13da-c74a-0fd8-74e0-3cdc547e4e08@shopee.com> (raw)
In-Reply-To: <20221215181803.ome46pkh6g7qu3t4@google.com>
On 2022/12/16 02:18, Shakeel Butt wrote:
> On Thu, Dec 15, 2022 at 09:19:07AM +0000, Haifeng Xu wrote:
>> The memory events aren't supported on root cgroup, so there is no need
>> to account MEMCG_OOM_KILL on root memcg.
>>
>
> Can you explain the scenario where this is happening and causing issue
> for you?
>
If the victim selected by oom killer belongs to root memcg, memcg_memory_event_mm
still counts the MEMCG_OOM_KILL event. This behavior is meaningless because the
flag of events/events.local in memory_files is CFTYPE_NOT_ON_ROOT. The root memcg
does not count any memory event.
>> Signed-off-by: Haifeng Xu <haifeng.xu@shopee.com>
>> ---
>> include/linux/memcontrol.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
>> index 567f12323f55..09f75161a3bc 100644
>> --- a/include/linux/memcontrol.h
>> +++ b/include/linux/memcontrol.h
>> @@ -1142,7 +1142,7 @@ static inline void memcg_memory_event_mm(struct mm_struct *mm,
>>
>> rcu_read_lock();
>> memcg = mem_cgroup_from_task(rcu_dereference(mm->owner));
>> - if (likely(memcg))
>> + if (likely(memcg && !mem_cgroup_is_root(memcg)))
>
> Even if we need this additional check, this is not the right place.
>
>> memcg_memory_event(memcg, event);
>> rcu_read_unlock();
>> }
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2022-12-16 1:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:19 Haifeng Xu
2022-12-15 18:18 ` Shakeel Butt
2022-12-16 1:43 ` Haifeng Xu [this message]
2022-12-16 6:42 ` Shakeel Butt
2022-12-16 7:28 ` Haifeng Xu
2022-12-16 7:36 ` Shakeel Butt
2022-12-16 7:50 ` Haifeng Xu
2022-12-16 8:17 ` Shakeel Butt
2022-12-16 8:37 ` Haifeng Xu
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=abec13da-c74a-0fd8-74e0-3cdc547e4e08@shopee.com \
--to=haifeng.xu@shopee.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=vasily.averin@linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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
all inboxes | Powered by JetHome®