From: "Wang Xiaoqiang" <wang_xiaoq@126.com>
To: Michal Hocko <mhocko@kernel.org>, vbabka <vbabka@suse.cz>,
n-horiguchi <n-horiguchi@ah.jp.nec.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re:Re: Question About Functions "__free_pages_check" and "check_new_page" in page_alloc.c
Date: Tue, 17 May 2016 09:06:38 +0800 (CST) [thread overview]
Message-ID: <5877fe6c.1e45.154bc401c81.Coremail.wang_xiaoq@126.com> (raw)
In-Reply-To: <20160516151657.GC23251@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
>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.
>will then print more detailed information.
>--
>Michal Hocko
>SUSE Labs
thank you, Michal.
[-- Attachment #2: Type: text/html, Size: 523 bytes --]
next prev parent reply other threads:[~2016-05-17 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 13:42 Wang Xiaoqiang
2016-05-16 15:16 ` Michal Hocko
2016-05-17 1:06 ` Wang Xiaoqiang [this message]
2016-05-17 5:14 ` Vlastimil Babka
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=5877fe6c.1e45.154bc401c81.Coremail.wang_xiaoq@126.com \
--to=wang_xiaoq@126.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.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