linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	mhocko@suse.com, Johannes Weiner <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,
	Tim Murray <timmurray@google.com>, Todd Kjos <tkjos@google.com>
Subject: Re: [PATCH v2] mm: terminate shrink_slab loop if signal is pending
Date: Fri, 8 Dec 2017 19:16:28 -0800	[thread overview]
Message-ID: <CAJuCfpEvzo1BAAj5AHLFqZnjbQg+s2njkzGBycEWJe1ZHuwO5w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1712081259520.47087@chino.kir.corp.google.com>

On Fri, Dec 8, 2017 at 1:02 PM, David Rientjes <rientjes@google.com> wrote:
> On Thu, 7 Dec 2017, 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.
>>
>
> I've proposed a similar patch in the past, but for a check on TIF_MEMDIE,
> which would today be a tsk_is_oom_victim(current), since we had observed
> lengthy stalls in reclaim that would have been prevented if the oom victim
> had exited out, returned back to the page allocator, allocated with
> ALLOC_NO_WATERMARKS, and proceeded to quickly exit.
>
> I'm not sure that all fatal_signal_pending() tasks should get the same
> treatment, but I understand the point that the task is killed and should
> free memory when it fully exits.  How much memory is unknown.
>

Thanks for the input. For my particular use case TIF_MEMDIE check
would not help because I'm trying to kill a process before OOM kicks
in, however the approach is interesting and provides food for thought.

>  > Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>>
>> ---
>> V2:
>> Sergey Senozhatsky:
>>   - Fix missing parentheses
>> ---
>>  mm/vmscan.c | 7 +++++++
>>  1 file changed, 7 insertions(+)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index c02c850ea349..28e4bdc72c16 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)))
>> +                     break;
>> +
>>               /*
>>                * If kernel memory accounting is disabled, we ignore
>>                * SHRINKER_MEMCG_AWARE flag and call all shrinkers

  reply	other threads:[~2017-12-09  3:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  1:23 [PATCH v2] mm: terminate shrink_slab loop if signal is pending Suren Baghdasaryan
2017-12-08  8:22 ` Michal Hocko
2017-12-08 11:36   ` Tetsuo Handa
2017-12-08 11:48     ` Michal Hocko
2017-12-08 14:03       ` Tetsuo Handa
2017-12-08 18:06         ` Suren Baghdasaryan
2017-12-09  8:08           ` Tetsuo Handa
2017-12-10 10:17             ` Michal Hocko
2017-12-11 21:05             ` Suren Baghdasaryan
2017-12-10 10:13           ` Michal Hocko
2017-12-10 11:37             ` Tetsuo Handa
2017-12-11 21:12             ` Suren Baghdasaryan
2017-12-08 21:02 ` David Rientjes
2017-12-09  3:16   ` Suren Baghdasaryan [this message]
2017-12-09 12:44   ` Tetsuo Handa

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=CAJuCfpEvzo1BAAj5AHLFqZnjbQg+s2njkzGBycEWJe1ZHuwO5w@mail.gmail.com \
    --to=surenb@google.com \
    --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=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=rientjes@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;
as well as URLs for NNTP newsgroup(s).