From: Doug Berger <opendmb@gmail.com>
To: Zi Yan <ziy@nvidia.com>
Cc: David Hildenbrand <david@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Eric Ren <renzhengeek@gmail.com>, Mike Rapoport <rppt@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Andrew Morton <akpm@linux-foundation.org>,
kernel test robot <lkp@intel.com>,
Qian Cai <quic_qiancai@quicinc.com>
Subject: Re: [PATCH v11 3/6] mm: make alloc_contig_range work at pageblock granularity
Date: Wed, 25 May 2022 14:03:05 -0700 [thread overview]
Message-ID: <fcac3340-31b5-8536-fd4e-ecb8a9aee2ae@gmail.com> (raw)
In-Reply-To: <F80CEC0E-0EA8-4210-8730-57D4D0CF0B23@nvidia.com>
On 5/25/2022 10:53 AM, Zi Yan wrote:
> On 25 May 2022, at 13:41, Doug Berger wrote:
>
>> I am seeing some free memory accounting problems with linux-next that I have bisected to this commit (i.e. b2c9e2fbba32 ("mm: make alloc_contig_range work at pageblock granularity").
>>
>> On an arm64 SMP platform with 4GB total memory and the default 16MB default CMA pool, I am seeing the following after boot with a sysrq Show Memory (e.g. 'echo m > /proc/sysrq-trigger'):
>>
>> [ 16.015906] sysrq: Show Memory
>> [ 16.019039] Mem-Info:
>> [ 16.021348] active_anon:14604 inactive_anon:919 isolated_anon:0
>> [ 16.021348] active_file:0 inactive_file:0 isolated_file:0
>> [ 16.021348] unevictable:0 dirty:0 writeback:0
>> [ 16.021348] slab_reclaimable:3662 slab_unreclaimable:3333
>> [ 16.021348] mapped:928 shmem:15146 pagetables:63 bounce:0
>> [ 16.021348] kernel_misc_reclaimable:0
>> [ 16.021348] free:976766 free_pcp:991 free_cma:7017
>> [ 16.056937] Node 0 active_anon:58416kB inactive_anon:3676kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:3712kB dirty:0kB writeback:0kB shmem:60584kB writeback_tmp:0kB kernel_stack:1200kB pagetables:252kB all_unreclaimable? no
>> [ 16.081526] DMA free:3041036kB boost:0kB min:6036kB low:9044kB high:12052kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:3145728kB managed:3029992kB mlocked:0kB bounce:0kB free_pcp:636kB local_pcp:0kB free_cma:28068kB
>> [ 16.108650] lowmem_reserve[]: 0 0 944 944
>> [ 16.112746] Normal free:866028kB boost:0kB min:1936kB low:2900kB high:3864kB reserved_highatomic:0KB active_anon:58416kB inactive_anon:3676kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:1048576kB managed:967352kB mlocked:0kB bounce:0kB free_pcp:3328kB local_pcp:864kB free_cma:0kB
>> [ 16.140393] lowmem_reserve[]: 0 0 0 0
>> [ 16.144133] DMA: 7*4kB (UMC) 4*8kB (M) 3*16kB (M) 3*32kB (MC) 5*64kB (M) 4*128kB (MC) 5*256kB (UMC) 7*512kB (UM) 5*1024kB (UM) 9*2048kB (UMC) 732*4096kB (MC) = 3027724kB
>> [ 16.159609] Normal: 149*4kB (UM) 95*8kB (UME) 26*16kB (UME) 8*32kB (ME) 2*64kB (UE) 1*128kB (M) 2*256kB (ME) 2*512kB (ME) 2*1024kB (UM) 0*2048kB 210*4096kB (M) = 866028kB
>> [ 16.175165] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
>> [ 16.183937] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB
>> [ 16.192533] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
>> [ 16.201040] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB
>> [ 16.209374] 15146 total pagecache pages
>> [ 16.213246] 0 pages in swap cache
>> [ 16.216595] Swap cache stats: add 0, delete 0, find 0/0
>> [ 16.221867] Free swap = 0kB
>> [ 16.224780] Total swap = 0kB
>> [ 16.227693] 1048576 pages RAM
>> [ 16.230694] 0 pages HighMem/MovableOnly
>> [ 16.234564] 49240 pages reserved
>> [ 16.237825] 4096 pages cma reserved
>>
>> Some anomolies in the above are:
>> free_cma:7017 with only 4096 pages cma reserved
>> DMA free:3041036kB with only managed:3029992kB
>>
>> I'm not sure what is going on here, but I am suspicious of split_free_page() since del_page_from_free_list doesn't affect migrate_type accounting, but __free_one_page() can.
>> Also PageBuddy(page) is being checked without zone->lock in isolate_single_pageblock().
>>
>> Please investigate this as well.
>
>
> Can you try this patch https://lore.kernel.org/linux-mm/20220524194756.1698351-1-zi.yan@sent.com/
> and see if it fixes the issue?
>
> Thanks.
>
The last hunk didn't apply directly to this commit, but I was able to
apply the patch to linux-next/master with no improvement to the free
memory accounting (actually anecdotaly worse):
[ 6.236828] sysrq: Show Memory
[ 6.239973] Mem-Info:
[ 6.242290] active_anon:14594 inactive_anon:924 isolated_anon:0
[ 6.242290] active_file:0 inactive_file:0 isolated_file:0
[ 6.242290] unevictable:0 dirty:0 writeback:0
[ 6.242290] slab_reclaimable:3671 slab_unreclaimable:3575
[ 6.242290] mapped:935 shmem:15147 pagetables:63 bounce:0
[ 6.242290] kernel_misc_reclaimable:0
[ 6.242290] free:1059009 free_pcp:1067 free_cma:90112
[ 6.278048] Node 0 active_anon:58376kB inactive_anon:3844kB
active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB
isolated(file):0kB mapped:3740kB dirty:0kB writeback:0kB shmem:60588kB
writeback_tmp:0kB kernel_stack:1216kB pagetables:252kB all_unreclaimable? no
[ 6.279422] arm-scmi brcm_scmi@0: timed out in resp(caller:
scmi_perf_level_set+0xe0/0x110)
[ 6.302501] DMA free:3372200kB boost:0kB min:6032kB low:9040kB
high:12048kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB
active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB
present:3145728kB managed:3029800kB mlocked:0kB bounce:0kB
free_pcp:636kB local_pcp:0kB free_cma:360448kB
[ 6.302515] lowmem_reserve[]: 0 0 944
[ 6.310894] cpufreq: __target_index: Failed to change cpu frequency: -110
[ 6.337920] 944
[ 6.337925] Normal free:863584kB boost:0kB min:1940kB low:2904kB
high:3868kB reserved_highatomic:0KB active_anon:58376kB
inactive_anon:3896kB active_file:0kB inactive_file:0kB unevictable:0kB
writepending:0kB present:1048576kB managed:967352kB mlocked:0kB
bounce:0kB free_pcp:3492kB local_pcp:828kB free_cma:0kB
[ 6.377782] lowmem_reserve[]: 0 0 0 0
[ 6.381461] DMA: 4*4kB (UM) 5*8kB (M) 3*16kB (M) 2*32kB (M) 6*64kB
(M) 5*128kB (M) 6*256kB (UM) 5*512kB (UM) 4*1024kB (M) 10*2048kB (UMC)
732*4096kB (MC) = 3028136kB
[ 6.396324] Normal: 84*4kB (U) 94*8kB (UM) 260*16kB (UME) 149*32kB
(UM) 99*64kB (UME) 39*128kB (UM) 12*256kB (U) 3*512kB (UME) 2*1024kB
(UM) 0*2048kB 204*4096kB (M) = 863584kB
[ 6.412054] Node 0 hugepages_total=0 hugepages_free=0
hugepages_surp=0 hugepages_size=1048576kB
[ 6.420770] Node 0 hugepages_total=0 hugepages_free=0
hugepages_surp=0 hugepages_size=32768kB
[ 6.429312] Node 0 hugepages_total=0 hugepages_free=0
hugepages_surp=0 hugepages_size=2048kB
[ 6.437767] Node 0 hugepages_total=0 hugepages_free=0
hugepages_surp=0 hugepages_size=64kB
[ 6.446047] 15147 total pagecache pages
[ 6.449890] 0 pages in swap cache
[ 6.453210] Swap cache stats: add 0, delete 0, find 0/0
[ 6.458445] Free swap = 0kB
[ 6.461331] Total swap = 0kB
[ 6.464217] 1048576 pages RAM
[ 6.467190] 0 pages HighMem/MovableOnly
[ 6.471032] 49288 pages reserved
[ 6.474267] 4096 pages cma reserved
Regards,
Doug
next prev parent reply other threads:[~2022-05-25 21:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:31 [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 1/6] mm: page_isolation: move has_unmovable_pages() to mm/page_isolation.c Zi Yan
2022-04-25 14:31 ` [PATCH v11 2/6] mm: page_isolation: check specified range for unmovable pages Zi Yan
2022-04-25 14:31 ` [PATCH v11 3/6] mm: make alloc_contig_range work at pageblock granularity Zi Yan
2022-04-29 13:54 ` Zi Yan
2022-05-24 19:00 ` Zi Yan
2022-05-25 17:41 ` Doug Berger
2022-05-25 17:53 ` Zi Yan
2022-05-25 21:03 ` Doug Berger [this message]
2022-05-25 21:11 ` Zi Yan
2022-05-26 17:34 ` Zi Yan
2022-05-26 19:46 ` Doug Berger
2022-04-25 14:31 ` [PATCH v11 4/6] mm: page_isolation: enable arbitrary range page isolation Zi Yan
2022-05-24 19:02 ` Zi Yan
2022-04-25 14:31 ` [PATCH v11 5/6] mm: cma: use pageblock_order as the single alignment Zi Yan
2022-04-25 14:31 ` [PATCH v11 6/6] drivers: virtio_mem: use pageblock size as the minimum virtio_mem size Zi Yan
2022-04-26 20:18 ` [PATCH v11 0/6] Use pageblock_order for cma and alloc_contig_range alignment Qian Cai
2022-04-26 20:26 ` Zi Yan
2022-04-26 21:08 ` Qian Cai
2022-04-26 21:38 ` Zi Yan
2022-04-27 12:41 ` Qian Cai
2022-04-27 13:10 ` Qian Cai
2022-04-27 13:27 ` Qian Cai
2022-04-27 13:30 ` Zi Yan
2022-04-27 21:04 ` Zi Yan
2022-04-28 12:33 ` Qian Cai
2022-04-28 12:39 ` Zi Yan
2022-04-28 16:19 ` Qian Cai
2022-04-29 13:38 ` Zi Yan
2022-05-19 20:57 ` Qian Cai
2022-05-19 21:35 ` Zi Yan
2022-05-19 23:24 ` Zi Yan
2022-05-20 11:30 ` Qian Cai
2022-05-20 13:43 ` Zi Yan
2022-05-20 14:13 ` Zi Yan
2022-05-20 19:41 ` Qian Cai
2022-05-20 21:56 ` Zi Yan
2022-05-20 23:41 ` Qian Cai
2022-05-22 16:54 ` Zi Yan
2022-05-22 19:33 ` Zi Yan
2022-05-24 16:59 ` Qian Cai
2022-05-10 1:03 ` Andrew Morton
2022-05-10 1:07 ` Zi Yan
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=fcac3340-31b5-8536-fd4e-ecb8a9aee2ae@gmail.com \
--to=opendmb@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=quic_qiancai@quicinc.com \
--cc=renzhengeek@gmail.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--cc=virtualization@lists.linux-foundation.org \
--cc=ziy@nvidia.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).