From: Andrew Morton <akpm@linux-foundation.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH] mm,page_alloc: Split stall warning and failure warning.
Date: Mon, 10 Apr 2017 15:03:08 -0700 [thread overview]
Message-ID: <20170410150308.c6e1a0213c32e6d587b33816@linux-foundation.org> (raw)
In-Reply-To: <1491825493-8859-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
On Mon, 10 Apr 2017 20:58:13 +0900 Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
> Patch "mm: page_alloc: __GFP_NOWARN shouldn't suppress stall warnings"
> changed to drop __GFP_NOWARN when calling warn_alloc() for stall warning.
> Although I suggested for two times to drop __GFP_NOWARN when warn_alloc()
> for stall warning was proposed, Michal Hocko does not want to print stall
> warnings when __GFP_NOWARN is given [1][2].
>
> "I am not going to allow defining a weird __GFP_NOWARN semantic which
> allows warnings but only sometimes. At least not without having a proper
> way to silence both failures _and_ stalls or just stalls. I do not
> really thing this is worth the additional gfp flag."
I interpret __GFP_NOWARN to mean "don't warn about this allocation
attempt failing", not "don't warn about anything at all". It's a very
minor issue but yes, methinks that stall warning should still come out.
Unless it's known to cause a problem for the stall warning to come out
for __GFP_NOWARN attempts? If so then perhaps a
__GFP_NOWARN_ABOUT_STALLS is needed?
--
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-04-10 22:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 11:58 Tetsuo Handa
2017-04-10 12:39 ` Michal Hocko
2017-04-10 14:23 ` Tetsuo Handa
2017-04-10 22:03 ` Andrew Morton [this message]
2017-04-11 7:15 ` Michal Hocko
2017-04-11 11:43 ` Tetsuo Handa
2017-04-11 11:54 ` Michal Hocko
2017-04-11 13:26 ` Tetsuo Handa
2017-04-17 22:48 ` David Rientjes
2017-04-18 11:49 ` Tetsuo Handa
2017-04-18 12:14 ` Michal Hocko
2017-04-18 21:47 ` David Rientjes
2017-04-19 11:13 ` Michal Hocko
2017-04-19 13:22 ` Stanislaw Gruszka
2017-04-19 13:33 ` Michal Hocko
2017-04-22 8:10 ` Stanislaw Gruszka
2017-04-24 8:42 ` Michal Hocko
2017-04-24 13:06 ` Stanislaw Gruszka
2017-04-24 15:06 ` Tetsuo Handa
2017-04-25 6:36 ` Stanislaw Gruszka
2017-04-19 22:34 ` David Rientjes
2017-04-20 11:46 ` 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=20170410150308.c6e1a0213c32e6d587b33816@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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