From: Michal Hocko <mhocko@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
akpm@linux-foundation.org, hannes@cmpxchg.org,
hillf.zj@alibaba-inc.com, minchan@kernel.org,
mgorman@techsingularity.net, ying.huang@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
timmurray@google.com, tkjos@google.com
Subject: Re: [PATCH] mm: terminate shrink_slab loop if signal is pending
Date: Thu, 7 Dec 2017 10:58:35 +0100 [thread overview]
Message-ID: <20171207095835.GE20234@dhcp22.suse.cz> (raw)
In-Reply-To: <20171207095223.GB574@jagdpanzerIV>
On Thu 07-12-17 18:52:23, Sergey Senozhatsky wrote:
> On (12/06/17 11:20), Suren Baghdasaryan wrote:
> > Slab shrinkers can be quite time consuming and when signal
> > is pending they can delay handling of the signal. If fatal
> > signal is pending there is no point in shrinking that process
> > since it will be killed anyway. This change checks for pending
> > fatal signals inside shrink_slab loop and if one is detected
> > terminates this loop early.
> >
> > Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> > ---
> > mm/vmscan.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index c02c850ea349..69296528ff33 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -486,6 +486,13 @@ static unsigned long shrink_slab(gfp_t gfp_mask, int nid,
> > .memcg = memcg,
> > };
> >
> > + /*
> > + * We are about to die and free our memory.
> > + * Stop shrinking which might delay signal handling.
> > + */
> > + if (unlikely(fatal_signal_pending(current))
>
> - if (unlikely(fatal_signal_pending(current))
> + if (unlikely(fatal_signal_pending(current)))
Heh, well, spotted. This begs a question how this has been tested, if at
all?
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-07 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 19:20 Suren Baghdasaryan
2017-12-06 23:26 ` Andrew Morton
2017-12-07 1:27 ` Suren Baghdasaryan
2017-12-07 8:34 ` Michal Hocko
2017-12-07 14:34 ` Tetsuo Handa
2017-12-08 0:44 ` Suren Baghdasaryan
2017-12-08 4:37 ` Suren Baghdasaryan
2017-12-08 4:40 ` Suren Baghdasaryan
2017-12-07 9:52 ` Sergey Senozhatsky
2017-12-07 9:58 ` Michal Hocko [this message]
2017-12-07 15:46 ` Suren Baghdasaryan
2017-12-07 16:25 ` Michal Hocko
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=20171207095835.GE20234@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=surenb@google.com \
--cc=timmurray@google.com \
--cc=tkjos@google.com \
--cc=ying.huang@intel.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