From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: mhocko@suse.com, 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: Wed, 6 Dec 2017 15:26:21 -0800 [thread overview]
Message-ID: <20171206152621.2c263569ea623dd1e0119848@linux-foundation.org> (raw)
In-Reply-To: <20171206192026.25133-1-surenb@google.com>
On Wed, 6 Dec 2017 11:20:26 -0800 Suren Baghdasaryan <surenb@google.com> 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.
Some quantification of "quite time consuming" and "delay" would be
interesting, please.
--
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-06 23:26 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 [this message]
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
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=20171206152621.2c263569ea623dd1e0119848@linux-foundation.org \
--to=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=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