From: Qian Cai <cai@lca.pw>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, Pavel.Tatashin@microsoft.com,
mingo@kernel.org, mgorman@techsingularity.net,
iamjoonsoo.kim@lge.com, tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm/page_owner: fix for deferred struct page init
Date: Fri, 4 Jan 2019 10:01:40 -0500 [thread overview]
Message-ID: <e4ad9d12-387d-1cc6-f404-cae6d43ccf80@lca.pw> (raw)
In-Reply-To: <20190104130906.GO31793@dhcp22.suse.cz>
On 1/4/19 8:09 AM, Michal Hocko wrote:
>> Here is the number without DEFERRED_STRUCT_PAGE_INIT.
>>
>> == page_ext_init() after page_alloc_init_late() ==
>> Node 0, zone DMA: page owner found early allocated 0 pages
>> Node 0, zone DMA32: page owner found early allocated 7009 pages
>> Node 0, zone Normal: page owner found early allocated 85827 pages
>> Node 4, zone Normal: page owner found early allocated 75063 pages
>>
>> == page_ext_init() before kmemleak_init() ==
>> Node 0, zone DMA: page owner found early allocated 0 pages
>> Node 0, zone DMA32: page owner found early allocated 6654 pages
>> Node 0, zone Normal: page owner found early allocated 41907 pages
>> Node 4, zone Normal: page owner found early allocated 41356 pages
>>
>> So, it told us that it will miss tens of thousands of early page allocation call
>> sites.
>
> This is an answer for the first part of the question (how much). The
> second is _do_we_care_?
Well, the purpose of this simple "ugly" ifdef is to avoid a regression for the
existing page_owner users with DEFERRED_STRUCT_PAGE_INIT deselected that would
start to miss tens of thousands early page allocation call sites.
The other option I can think of to not hurt your eyes is to rewrite the whole
page_ext_init(), init_page_owner(), init_debug_guardpage() to use all early
functions, so it can work in both with DEFERRED_STRUCT_PAGE_INIT=y and without.
However, I have a hard-time to convince myself it is a sensible thing to do.
next prev parent reply other threads:[~2019-01-04 15:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 22:31 kernel panic with page_owner=on Qian Cai
2018-12-19 1:57 ` [PATCH] mm: skip checking poison pattern for page_to_nid() Qian Cai
2018-12-19 10:20 ` Michal Hocko
2018-12-19 12:46 ` Qian Cai
2018-12-20 6:03 ` [PATCH] mm/page_owner: fix for deferred struct page init Qian Cai
2018-12-20 9:22 ` Michal Hocko
2018-12-20 18:50 ` [PATCH v2] " Qian Cai
2018-12-20 20:31 ` [PATCH v3] " Qian Cai
2018-12-20 21:00 ` William Kucharski
2018-12-20 21:04 ` Qian Cai
2018-12-20 21:04 ` Qian Cai
2019-01-03 11:51 ` Michal Hocko
2019-01-03 16:38 ` Qian Cai
2019-01-03 16:59 ` Michal Hocko
2019-01-03 17:38 ` Qian Cai
2019-01-03 19:07 ` Michal Hocko
2019-01-03 19:53 ` Qian Cai
2019-01-03 20:22 ` Michal Hocko
2019-01-03 22:22 ` Qian Cai
2019-01-04 13:09 ` Michal Hocko
2019-01-04 15:01 ` Qian Cai [this message]
2019-01-04 15:17 ` Michal Hocko
2019-01-04 15:25 ` Qian Cai
2019-01-04 15:32 ` Michal Hocko
2019-01-04 20:18 ` Qian Cai
2019-01-07 18:43 ` Michal Hocko
2019-01-08 1:53 ` Qian Cai
2019-01-08 8:20 ` Michal Hocko
2019-01-08 13:19 ` Qian Cai
2019-01-08 13:19 ` Qian Cai
2019-01-08 22:02 ` Andrew Morton
2019-01-08 22:13 ` Qian Cai
2019-01-08 22:40 ` Michal Hocko
2019-01-09 7:34 ` [PATCH v2] " Michal Hocko
2019-01-15 20:28 ` [PATCH] Revert "mm: use early_pfn_to_nid in page_ext_init" Qian Cai
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=e4ad9d12-387d-1cc6-f404-cae6d43ccf80@lca.pw \
--to=cai@lca.pw \
--cc=Pavel.Tatashin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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