From: Mel Gorman <mgorman@suse.de>
To: Michal Hocko <mhocko@suse.com>
Cc: linux-mm@kvack.org, Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm: reduce noise in show_mem for lowmem allocations
Date: Wed, 24 Aug 2022 14:34:51 +0100 [thread overview]
Message-ID: <20220824133451.6kqttzm5t4iigz2i@suse.de> (raw)
In-Reply-To: <YwScVmVofIZkopkF@dhcp22.suse.cz>
On Tue, Aug 23, 2022 at 11:22:30AM +0200, Michal Hocko wrote:
> Hi,
> while discussing early DMA pool pre-allocation failure with Christoph
> [1] I have realized that the allocation failure warning is rather noisy
> for constrained allocations like GFP_DMA{32}. Those zones are usually
> not populated on all nodes very often as their memory ranges are
> constrained.
>
> This is an attempt to reduce the ballast that doesn't provide any
> relevant information for those allocation failures investigation.
> Please note that I have only compile tested it (in my default config
> setup) and I am throwing it mostly to see what people think about it.
>
> [1] http://lkml.kernel.org/r/20220817060647.1032426-1-hch@lst.de
No objections.
--
Mel Gorman
SUSE Labs
next parent reply other threads:[~2022-08-24 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YwScVmVofIZkopkF@dhcp22.suse.cz>
2022-08-24 13:34 ` Mel Gorman [this message]
2022-08-25 9:52 ` Vlastimil Babka
2022-08-25 9:59 ` Michal Hocko
2022-08-26 7:37 ` Vlastimil Babka
2022-08-25 15:19 ` Johannes Weiner
2022-08-30 7:34 ` Michal Hocko
2022-09-01 14:14 ` Vlastimil Babka
2022-09-01 19:18 ` 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=20220824133451.6kqttzm5t4iigz2i@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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