From: Michal Hocko <mhocko@suse.com>
To: David Hildenbrand <david@redhat.com>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
joaodias@google.com
Subject: Re: [PATCH] mm: be more verbose for alloc_contig_range faliures
Date: Mon, 8 Mar 2021 15:11:02 +0100 [thread overview]
Message-ID: <YEYwdjvYGiZ4crMt@dhcp22.suse.cz> (raw)
In-Reply-To: <c1461e51-7ad0-7fb5-9dc2-7f7c5cdf128f@redhat.com>
On Mon 08-03-21 14:22:12, David Hildenbrand wrote:
> On 08.03.21 13:49, Michal Hocko wrote:
[...]
> > Earlier in the discussion I have suggested dynamic debugging facility.
> > Documentation/admin-guide/dynamic-debug-howto.rst. Have you tried to
> > look into that direction?
>
> Did you see the previous mail this is based on:
>
> https://lkml.kernel.org/r/YEEUq8ZRn4WyYWVx@google.com
>
> I agree that "nofail" is misleading. Rather something like
> "dump_on_failure", just a better name :)
Yeah, I have read through the email thread. I just do not get why we
cannot make it pr_debug() and add -DDYNAMIC_DEBUG_MODULE for
page_alloc.c (I haven't checked whether that is possible for built in
compile units, maybe it is not but from a quick seems it should).
I really do not like this to be a part of the API. alloc_contig_range is
a best effort allocator. Complaining about failure is too noisy. I do
agree that some sort of easy to enable debugging is due but please let's
make it as transparent to the code as possible.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-03-08 14:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 16:36 Minchan Kim
2021-02-17 16:51 ` David Hildenbrand
2021-02-17 17:26 ` Minchan Kim
2021-02-17 17:34 ` David Hildenbrand
2021-02-17 17:45 ` Minchan Kim
2021-02-18 8:56 ` Michal Hocko
2021-02-18 9:02 ` David Hildenbrand
2021-02-18 9:35 ` Michal Hocko
2021-02-18 9:43 ` David Hildenbrand
2021-02-18 9:59 ` Michal Hocko
2021-02-18 16:19 ` Minchan Kim
2021-02-18 16:26 ` David Hildenbrand
2021-02-18 16:47 ` Minchan Kim
2021-02-18 16:53 ` David Hildenbrand
2021-02-19 9:28 ` Michal Hocko
2021-02-19 9:30 ` David Hildenbrand
2021-02-19 10:02 ` Michal Hocko
2021-02-19 10:34 ` David Hildenbrand
[not found] ` <YD50pcPuwV456vwm@google.com>
2021-03-04 16:01 ` Minchan Kim
2021-03-04 16:10 ` David Hildenbrand
2021-03-04 16:23 ` Minchan Kim
2021-03-04 16:28 ` David Hildenbrand
2021-03-04 17:11 ` Minchan Kim
2021-03-04 17:23 ` David Hildenbrand
2021-03-04 18:11 ` Minchan Kim
2021-03-04 18:22 ` Minchan Kim
2021-03-08 12:49 ` Michal Hocko
2021-03-08 13:22 ` David Hildenbrand
2021-03-08 14:11 ` Michal Hocko [this message]
2021-03-08 14:13 ` David Hildenbrand
2021-03-08 15:42 ` Michal Hocko
2021-03-08 15:58 ` Minchan Kim
2021-03-08 16:21 ` Michal Hocko
2021-03-08 17:01 ` Minchan Kim
2021-03-08 20:27 ` Minchan Kim
2021-02-18 16:10 ` Minchan Kim
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=YEYwdjvYGiZ4crMt@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=joaodias@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@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