From: Suren Baghdasaryan <surenb@google.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
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] mm: terminate shrink_slab loop if signal is pending
Date: Thu, 7 Dec 2017 20:40:33 -0800 [thread overview]
Message-ID: <CAJuCfpE+iM0r3E-eeBGDDo5k=i8qar+im+STfsMG75fc+Vpm6w@mail.gmail.com> (raw)
In-Reply-To: <CAJuCfpHV=O4Kq4jppeMu7A==N37VhmXvHYRYvERmxQVeEZ=jUQ@mail.gmail.com>
> According to my traces this 43ms could drop to the average of 11ms and
> worst case 25ms if throttle_direct_reclaim would return true when
> fatal signal is pending but I would like to hear your opinion about
> throttle_direct_reclaim logic.
Digging some more into this I realize my last statement might be
incorrect. Throttling in this situation might not help with the signal
handling delay because of the logic in __alloc_pages_slowpath. I'll
have to experiment with this first, please disregard that last
statement for now.
--
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-08 4:40 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 [this message]
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='CAJuCfpE+iM0r3E-eeBGDDo5k=i8qar+im+STfsMG75fc+Vpm6w@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--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