From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mhocko@kernel.org, hannes@cmpxchg.org,
mgorman@techsingularity.net, david@fromorbit.com,
apolyakov@beget.ru, lists@wiesinger.com, hughd@google.com
Subject: Re: [PATCH v8] mm: Add memory allocation watchdog kernel thread.
Date: Thu, 6 Apr 2017 20:02:24 +0900 [thread overview]
Message-ID: <201704062002.FAE18212.OJOFOHLStFVFQM@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1489578541-81526-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
Andrew, anything else I can do?
Tetsuo Handa wrote:
> Regarding maintenance burden, I consider this patch is least invasive
> because it does not make __GFP_NOWARN flag's semantic confusing while
> providing administrators some hints [4]. Also, this patch will remain
> useful because we might overlook something that can cause infinite
> loop (or significant delay) in future changes, and we can remove this
> patch when we achieve safe and robust memory management subsystem.
>
> Changes from v7 [11]:
>
> (1) Reflect review comments from Andrew Morton. (Convert "u8 type" to
> "bool report", use CPUHP_PAGE_ALLOC_DEAD event and replace
> for_each_possible_cpu() with for_each_online_cpu(), reuse existing
> rcu_lock_break() and hung_timeout_jiffies() for now, update comments).
We are still sometimes overlooking unexpected delays like
http://lkml.kernel.org/r/alpine.LSU.2.11.1704051331420.4288@eggly.anvils and
http://lkml.kernel.org/r/da13c3c7-b514-67b0-2eb9-6d6af277901b@wiesinger.com
and I think we will in the future. I believe that this patch is helpful for
catching such cases.
--
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>
prev parent reply other threads:[~2017-04-06 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 11:49 Tetsuo Handa
2017-04-06 11:02 ` Tetsuo Handa [this message]
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=201704062002.FAE18212.OJOFOHLStFVFQM@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=apolyakov@beget.ru \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lists@wiesinger.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
/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