From: zhong jiang <zhongjiang-ali@linux.alibaba.com>
To: hannes@cmpxchg.org, mhocko@kernel.org, akpm@linux-foundation.org
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] memcg, oom: check memcg margin for parallel oom
Date: Mon, 9 Nov 2020 15:56:53 +0800 [thread overview]
Message-ID: <789efc6a-c71c-ef34-176f-2e4b0ce1eddf@linux.alibaba.com> (raw)
In-Reply-To: <1604652665-13640-1-git-send-email-zhongjiang-ali@linux.alibaba.com>
I am sorry for my stupid email. Please ignore it. Thanks😅
On 2020/11/6 4:51 下午, zhongjiang-ali wrote:
> From: Yafang Shao <laoar.shao@gmail.com>
>
> Memcg oom killer invocation is synchronized by the global oom_lock and
> tasks are sleeping on the lock while somebody is selecting the victim or
> potentially race with the oom_reaper is releasing the victim's memory.
> This can result in a pointless oom killer invocation because a waiter
> might be racing with the oom_reaper
>
> P1 oom_reaper P2
> oom_reap_task mutex_lock(oom_lock)
> out_of_memory # no victim because we have one already
> __oom_reap_task_mm mute_unlock(oom_lock)
> mutex_lock(oom_lock)
> set MMF_OOM_SKIP
> select_bad_process
> # finds a new victim
>
> The page allocator prevents from this race by trying to allocate after the
> lock can be acquired (in __alloc_pages_may_oom) which acts as a last
> minute check. Moreover page allocator simply doesn't block on the
> oom_lock and simply retries the whole reclaim process.
>
> Memcg oom killer should do the last minute check as well. Call
> mem_cgroup_margin to do that. Trylock on the oom_lock could be done as
> well but this doesn't seem to be necessary at this stage.
>
> [mhocko@kernel.org: commit log]
>
> Suggested-by: Michal Hocko <mhocko@kernel.org>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Acked-by: Michal Hocko <mhocko@suse.com>
> Acked-by: Chris Down <chris@chrisdown.name>
> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Link: http://lkml.kernel.org/r/1594735034-19190-1-git-send-email-laoar.shao@gmail.com
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>
> ---
> mm/memcontrol.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index b30a52d..369d9e1 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1663,15 +1663,21 @@ static bool mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
> .gfp_mask = gfp_mask,
> .order = order,
> };
> - bool ret;
> + bool ret = true;
>
> if (mutex_lock_killable(&oom_lock))
> return true;
> +
> + if (mem_cgroup_margin(memcg) >= (1 << order))
> + goto unlock;
> +
> /*
> * A few threads which were not waiting at mutex_lock_killable() can
> * fail to bail out. Therefore, check again after holding oom_lock.
> */
> ret = should_force_charge() || out_of_memory(&oc);
> +
> +unlock:
> mutex_unlock(&oom_lock);
> return ret;
> }
prev parent reply other threads:[~2020-11-09 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 8:51 zhongjiang-ali
2020-11-09 7:56 ` zhong jiang [this message]
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=789efc6a-c71c-ef34-176f-2e4b0ce1eddf@linux.alibaba.com \
--to=zhongjiang-ali@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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