[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <C10223BC-1156-43FB-B7D9-674076AFDE19@lca.pw>
Date: Fri, 6 Mar 2020 22:31:39 -0500
From: Qian Cai <cai@....pw>
To: Alex Shi <alex.shi@...ux.alibaba.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>, aarcange@...hat.com,
daniel.m.jordan@...cle.com, hannes@...xchg.org, hughd@...gle.com,
khlebnikov@...dex-team.ru, kirill@...temov.name,
kravetz@...ibm.com, mhocko@...nel.org, mm-commits@...r.kernel.org,
tj@...nel.org, vdavydov.dev@...il.com, willy@...radead.org,
yang.shi@...ux.alibaba.com
Subject: Re: [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch
removed from -mm tree
> On Mar 6, 2020, at 10:26 PM, Alex Shi <alex.shi@...ux.alibaba.com> wrote:
>
> 在 2020/3/7 上午10:27, Qian Cai 写道:
>>> Compare to this patch's change, the 'c8cba0cc2a80 mm/thp: narrow lru locking' is more
>>> likely bad. Maybe it's due to lru unlock was moved before ClearPageCompound() from
>>> before remap_page(head); guess this unlock should be move after ClearPageCompound or
>>> move back to origin place.
>> I can only confirmed that after reverted those 6 patches, I am no long be able to reproduce it.
>>
>
> Hi Qian,
>
> Thanks for response!
> Could you like just try to revert the patch: 'mm/thp: narrow lru locking'? or would you like to
> share me info of your tests and let me reproduce it? like kernel config, system ENV, machine type.
> I had run hundreds cycle of oom01, but akpm kernel(f2cbd107a99b) still survived.
https://raw.githubusercontent.com/cailca/linux-mm/master/x86.config
HPE ProLiant DL385 Gen10
AMD EPYC 7601 32-Core Processor
65536 MB memory, 400 GB disk space
Processors 128
Cores 64
Sockets 2
linux-next 20200306
>
> I got my ltp mm testing results, it run total 75 cases, failed 2, skip 9 and others are success
> and kernel works well after test on yesterday's akmp head: f2cbd107a99b.
>
> Many Thanks for help!
> Alex
>
> =====
>
> Test Start Time: Fri Mar 6 20:49:59 2020
> -----------------------------------------
> Testcase Result Exit Value
> -------- ------ ----------
> mm01 PASS 0
> mm02 PASS 0
> mtest01 PASS 0
> mtest01w PASS 0
> mtest05 PASS 0
> mtest06 PASS 0
> mtest06_2 PASS 0
> mtest06_3 PASS 0
> mem01 PASS 0
> mem02 PASS 0
> mem03 PASS 0
> page01 PASS 0
> page02 PASS 0
> data_space PASS 0
> stack_space PASS 0
> shmt02 PASS 0
> shmt03 PASS 0
> shmt04 PASS 0
> shmt05 PASS 0
> shmt06 PASS 0
> shmt07 PASS 0
> shmt08 PASS 0
> shmt09 PASS 0
> shmt10 PASS 0
> shm_test01 PASS 0
> mallocstress01 PASS 0
> mmapstress01 PASS 0
> mmapstress02 PASS 0
> mmapstress03 PASS 0
> mmapstress04 PASS 0
> mmapstress05 PASS 0
> mmapstress06 PASS 0
> mmapstress07 PASS 0
> mmapstress08 PASS 0
> mmapstress09 PASS 0
> mmapstress10 PASS 0
> mmap10 PASS 0
> mmap10_1 PASS 0
> mmap10_2 PASS 0
> mmap10_3 PASS 0
> mmap10_4 PASS 0
> ksm01 FAIL 2
> ksm01_1 FAIL 1
> ksm02 CONF 32
> ksm02_1 CONF 32
> ksm03 PASS 0
> ksm03_1 PASS 0
> ksm04 CONF 32
> ksm04_1 CONF 32
> ksm05 PASS 0
> ksm06 CONF 32
> ksm06_1 CONF 32
> ksm06_2 CONF 32
> oom01 PASS 0
> oom02 CONF 32
> oom03 PASS 0
> oom04 PASS 0
> oom05 PASS 0
> swapping01 PASS 0
> thp01 PASS 0
> thp02 PASS 0
> thp03 PASS 0
> vma01 PASS 0
> vma02 PASS 0
> vma03 CONF 32
> vma04 PASS 0
> vma05 PASS 0
> overcommit_memory01 PASS 0
> overcommit_memory02 PASS 0
> overcommit_memory03 PASS 0
> overcommit_memory04 PASS 0
> overcommit_memory05 PASS 0
> overcommit_memory06 PASS 0
> max_map_count PASS 0
> min_free_kbytes PASS 0
>
> -----------------------------------------------
> Total Tests: 75
> Total Skipped Tests: 9
> Total Failures: 2
> Kernel Version: 5.6.0-rc4-06724-gf2cbd107a99b
> Machine Architecture: x86_64
> Hostname: alexshi-test
>
Powered by blists - more mailing lists