From: Vlastimil Babka <vbabka@suse.cz>
To: Wang Xiaoqiang <wang_xiaoq@126.com>,
Michal Hocko <mhocko@kernel.org>,
n-horiguchi <n-horiguchi@ah.jp.nec.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: Question About Functions "__free_pages_check" and "check_new_page" in page_alloc.c
Date: Tue, 17 May 2016 07:14:42 +0200 [thread overview]
Message-ID: <573AA8C2.2060606@suse.cz> (raw)
In-Reply-To: <5877fe6c.1e45.154bc401c81.Coremail.wang_xiaoq@126.com>
On 05/17/2016 03:06 AM, Wang Xiaoqiang wrote:
>>yes it would. Why that would matter. The checks should be in an order
>>which could give us a more specific reason with later checks. bad_page()
>
> I see, you mean the later "bad_reason" is the superset of the previous one.
Not exactly. It's not possible to sort all the reasons like that. But as
Michal said, bad_page() will print all the relevant info so you can
reconstruct all reasons from it. The bad_reason text is mostly a hint
what to check first.
>>will then print more detailed information.
>>--
>>Michal Hocko
>>SUSE Labs
>
> thank you, Michal.
>
>
>
>
--
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:[~2016-05-17 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 13:42 Question About Functions "__free_pages_check" and "check_new_page" in page_alloc.c Wang Xiaoqiang
2016-05-16 15:16 ` Michal Hocko
2016-05-17 1:06 ` Wang Xiaoqiang
2016-05-17 5:14 ` Vlastimil Babka [this message]
2016-05-17 8:17 ` Wang Xiaoqiang
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=573AA8C2.2060606@suse.cz \
--to=vbabka@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=wang_xiaoq@126.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).