From: Vlastimil Babka <vbabka@suse.cz>
To: Sandipan Das <sandipan@linux.ibm.com>, Michal Hocko <mhocko@suse.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
khlebnikov@yandex-team.ru, kirill@shutemov.name,
aneesh.kumar@linux.ibm.com, srikar@linux.vnet.ibm.com
Subject: Re: [PATCH] mm: vmstat: Use zeroed stats for unpopulated zones
Date: Thu, 7 May 2020 13:07:05 +0200 [thread overview]
Message-ID: <a83b7475-56f5-8ea0-e1c8-a9d5b6bb8896@suse.cz> (raw)
In-Reply-To: <1041ca78-edac-6a22-a843-c8d439133d2b@linux.ibm.com>
On 5/7/20 11:08 AM, Sandipan Das wrote:
>>>
>>> This is certainly an improvement. Thanks! The question whether we can
>>> identify where bogus numbers came from would be interesting as well.
>>> Maybe those are not worth fixing but it would be great to understand
>>> them at least. I have to say that the explanation via boot_pageset is
>>> not really clear to me.
>>>
>>
>> The documentation update will definitely help. Thanks for that.
Thanks both, will send a proper patch.
>> I did collect some stack traces on a ppc64 guest for calls to zone_statistics()
>> in case of zones that are using the boot_pageset and most of them originate
>> from kmem_cache_init() with eventual calls to allocate_slab().
>>
>> [ 0.000000] [c00000000282b690] [c000000000402d98] zone_statistics+0x138/0x1d0
>> [ 0.000000] [c00000000282b740] [c000000000401190] rmqueue_pcplist+0xf0/0x120
>> [ 0.000000] [c00000000282b7d0] [c00000000040b178] get_page_from_freelist+0x2f8/0x2100
>> [ 0.000000] [c00000000282bb30] [c000000000401ae0] __alloc_pages_nodemask+0x1a0/0x2d0
>> [ 0.000000] [c00000000282bbc0] [c00000000044b040] alloc_slab_page+0x70/0x580
>> [ 0.000000] [c00000000282bc20] [c00000000044b5f8] allocate_slab+0xa8/0x610
>> ...
>>
>> In the remaining cases, the sources are ftrace_init() and early_trace_init().
>>
>
> Forgot to add that this happens during the period between zone_pcp_init() and setup_zone_pageset().
If you can identify a good moment during the boot when the boot_pageset stops
being used, maybe we could just reset its stats to zero once at that point and
be done with it.
> - Sandipan
>
next prev parent reply other threads:[~2020-05-07 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 7:03 Sandipan Das
2020-05-04 10:26 ` Michal Hocko
2020-05-06 13:33 ` Vlastimil Babka
2020-05-06 14:02 ` Michal Hocko
2020-05-06 15:09 ` Vlastimil Babka
2020-05-06 15:24 ` Michal Hocko
2020-05-06 15:50 ` Vlastimil Babka
2020-05-07 7:09 ` Michal Hocko
2020-05-07 9:05 ` Sandipan Das
2020-05-07 9:08 ` Sandipan Das
2020-05-07 11:07 ` Vlastimil Babka [this message]
2020-05-07 11:17 ` Sandipan Das
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=a83b7475-56f5-8ea0-e1c8-a9d5b6bb8896@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=sandipan@linux.ibm.com \
--cc=srikar@linux.vnet.ibm.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