From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@suse.de>,
David Rientjes <rientjes@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] GFP_NOFAIL reserves + warning about reserves depletion
Date: Wed, 25 Nov 2015 11:40:52 +0100 [thread overview]
Message-ID: <1448448054-804-1-git-send-email-mhocko@kernel.org> (raw)
Hi,
The first patch has been posted [1] last time and it seems there is no
major opposition to it. The only concern was a warning which was used
to note the ALLOC_NO_WATERMARKS request for the __GFP_NOFAIL failed.
I still think that the warning is helpful so I've separated it to
its own patch 2 and make it more generic to all ALLOC_NO_WATERMARKS
failures. The warning is on off but an update to min_free_kbytes
allows dump the warning again.
[1] http://lkml.kernel.org/r/1447249697-13380-1-git-send-email-mhocko@kernel.org
--
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 reply other threads:[~2015-11-25 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 10:40 Michal Hocko [this message]
2015-11-25 10:40 ` [PATCH 1/2] mm, oom: Give __GFP_NOFAIL allocations access to memory reserves Michal Hocko
2015-11-25 10:51 ` David Rientjes
2015-11-25 11:18 ` Michal Hocko
2015-11-25 20:57 ` David Rientjes
2015-11-26 9:34 ` Michal Hocko
2015-11-30 22:17 ` David Rientjes
2015-12-02 15:07 ` Michal Hocko
2015-12-02 15:13 ` [PATCH v2] " Michal Hocko
2015-12-03 0:01 ` David Rientjes
2015-11-25 10:40 ` [PATCH 2/2] mm: warn about ALLOC_NO_WATERMARKS request failures Michal Hocko
2015-11-25 10:59 ` David Rientjes
2015-11-25 11:55 ` Michal Hocko
2015-11-25 21:01 ` David Rientjes
2015-11-26 9:52 ` Michal Hocko
2015-11-30 22:24 ` David Rientjes
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=1448448054-804-1-git-send-email-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).