From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [patch] mm, oom: stop reclaiming if GFP_ATOMIC will start failing soon
Date: Wed, 29 Apr 2020 08:37:20 +0900 [thread overview]
Message-ID: <bba0dd4b-6f38-84e0-ffbf-fbf4243b6c43@i-love.sakura.ne.jp> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2004281436280.131129@chino.kir.corp.google.com>
On 2020/04/29 6:48, David Rientjes wrote:
> Somewhat related to what I described in the changelog: we lost the "page
> allocation stalls" artifacts in the kernel log for 4.15. The commit
> description references an asynchronous mechanism for getting this
> information; I don't know where this mechanism currently lives.
The asynchronous mechanism I meant in that commit is
https://lkml.kernel.org/r/c9c87635-6e00-5ce7-b05a-966011c8fe3f@I-love.SAKURA.ne.jp .
We are still forced to live in a world where we cannot get a clue for stalled allocations. :-(
next prev parent reply other threads:[~2020-04-28 23:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 20:48 David Rientjes
2020-04-25 0:32 ` Tetsuo Handa
2020-04-26 0:27 ` Andrew Morton
2020-04-26 3:04 ` Tetsuo Handa
2020-04-27 3:12 ` David Rientjes
2020-04-27 5:03 ` Tetsuo Handa
2020-04-27 20:30 ` Andrew Morton
2020-04-27 23:03 ` David Rientjes
2020-04-27 23:35 ` Andrew Morton
2020-04-28 7:43 ` Michal Hocko
2020-04-29 8:31 ` peter enderborg
2020-04-29 9:00 ` Michal Hocko
2020-04-28 9:38 ` Vlastimil Babka
2020-04-28 21:48 ` David Rientjes
2020-04-28 23:37 ` Tetsuo Handa [this message]
2020-04-29 7:51 ` Vlastimil Babka
2020-04-29 9:04 ` Michal Hocko
2020-04-29 10:45 ` Tetsuo Handa
2020-04-29 11:43 ` Michal Hocko
2020-04-27 8:20 ` peter enderborg
2020-04-27 15:01 ` 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=bba0dd4b-6f38-84e0-ffbf-fbf4243b6c43@i-love.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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