From: Michal Hocko <mhocko@suse.com>
To: Yang Shi <shy828301@gmail.com>
Cc: Julius Hemanth Pitti <jpitti@cisco.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guro@fb.com>, Cgroups <cgroups@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xe-linux-external@cisco.com
Subject: Re: [PATCH v2] mm: memcg: yield cpu when we fail to charge pages
Date: Tue, 8 Sep 2020 22:53:10 +0200 [thread overview]
Message-ID: <20200908205310.GF26850@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHbLzkqYrkA6=RSBpwEQJ5WaLUWwdP=05BPE2F4pRgk98NuVTg@mail.gmail.com>
On Tue 08-09-20 13:31:51, Yang Shi wrote:
> On Tue, Sep 8, 2020 at 1:14 PM Julius Hemanth Pitti <jpitti@cisco.com> wrote:
> >
> > For non root CG, in try_charge(), we keep trying
> > to charge until we succeed. On non-preemptive
> > kernel, when we are OOM, this results in holding
> > CPU forever.
> >
> > On SMP systems, this doesn't create a big problem
> > because oom_reaper get a change to kill victim
> > and make some free pages. However on a single-core
> > CPU (or cases where oom_reaper pinned to same CPU
> > where try_charge is executing), oom_reaper shall
> > never get scheduled and we stay in try_charge forever.
> >
> > Steps to repo this on non-smp:
> > 1. mount -t tmpfs none /sys/fs/cgroup
> > 2. mkdir /sys/fs/cgroup/memory
> > 3. mount -t cgroup none /sys/fs/cgroup/memory -o memory
> > 4. mkdir /sys/fs/cgroup/memory/0
> > 5. echo 40M > /sys/fs/cgroup/memory/0/memory.limit_in_bytes
> > 6. echo $$ > /sys/fs/cgroup/memory/0/tasks
> > 7. stress -m 5 --vm-bytes 10M --vm-hang 0
>
> Isn't it the same problem solved by e3336cab2579 ("mm: memcg: fix
> memcg reclaim soft lockup")? It has been in Linus's tree.
Yes it should because it adds a scheduling point regardless
of reclaimability.
> > Signed-off-by: Julius Hemanth Pitti <jpitti@cisco.com>
> > Acked-by: Roman Gushchin <guro@fb.com>
> > ---
> >
> > Changes in v2:
> > - Added comments.
> > - Added "Acked-by: Roman Gushchin <guro@fb.com>".
> > ---
> > mm/memcontrol.c | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index cfa6cbad21d5..4f293bf8c7ed 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -2745,6 +2745,15 @@ static int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask,
> > if (fatal_signal_pending(current))
> > goto force;
> >
> > + /*
> > + * We failed to charge even after retries, give oom_reaper or
> > + * other process a change to make some free pages.
> > + *
> > + * On non-preemptive, Non-SMP system, this is critical, else
> > + * we keep retrying with no success, forever.
> > + */
> > + cond_resched();
> > +
> > /*
> > * keep retrying as long as the memcg oom killer is able to make
> > * a forward progress or bypass the charge if the oom killer
> > --
> > 2.17.1
> >
> >
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-09-08 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:14 Julius Hemanth Pitti
2020-09-08 20:31 ` Yang Shi
2020-09-08 20:53 ` Michal Hocko [this message]
2020-09-08 20:57 ` Julius Hemanth Pitti (jpitti)
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=20200908205310.GF26850@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=jpitti@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=vdavydov.dev@gmail.com \
--cc=xe-linux-external@cisco.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