From: Qian Cai <cai@lca.pw>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
aarcange@redhat.com, daniel.m.jordan@oracle.com,
hannes@cmpxchg.org, khlebnikov@yandex-team.ru,
kirill@shutemov.name, kravetz@us.ibm.com, mhocko@kernel.org,
mm-commits@vger.kernel.org, tj@kernel.org,
vdavydov.dev@gmail.com, yang.shi@linux.alibaba.com,
linux-mm@kvack.org
Subject: Re: [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch removed from -mm tree
Date: Thu, 5 Mar 2020 23:46:26 -0500 [thread overview]
Message-ID: <1E0DE356-9F9B-4E00-9F53-85E2FED99CF2@lca.pw> (raw)
In-Reply-To: <9eb3efe1-f203-c3b1-679d-5e158fd8639f@linux.alibaba.com>
> On Mar 5, 2020, at 11:42 PM, Alex Shi <alex.shi@linux.alibaba.com> wrote:
>
>
>
> 在 2020/3/6 下午12:17, Hugh Dickins 写道:
>> On Thu, 5 Mar 2020, Qian Cai wrote:
>>>> On Mar 5, 2020, at 10:38 PM, Matthew Wilcox <willy@infradead.org> wrote:
>>>>
>>>> On Thu, Mar 05, 2020 at 10:32:18PM -0500, Qian Cai wrote:
>>>>>> On Mar 5, 2020, at 9:50 PM, akpm@linux-foundation.org wrote:
>>>>>> The patch titled
>>>>>> Subject: mm/vmscan: remove unnecessary lruvec adding
>>>>>> has been removed from the -mm tree. Its filename was
>>>>>> mm-vmscan-remove-unnecessary-lruvec-adding.patch
>>>>>>
>>>>>> This patch was dropped because it had testing failures
>>>>> Andrew, do you have more information about this failure? I hit a bug
>>>>> here under memory pressure and am wondering if this is related
>>>>> which might save me some time digging…
>> Very likely related.
>>
>
> Hi all,
>
> Apologize for the trouble!
> And Many thanks for you all for the report!
> Obviously, I missed memory stress testing which I should do. Apologize again!
>
> Qian Cai,
> Which test case are you using? Could you share the reproduce steps for me?
LTP oom01 in a tight loop with swap,
# i=0; while :; do echo $((i++)); oom01; sleep 5; done
>
> Hugh,
> Many thanks for help! I will seek some memory stress case and waiting for your case.
>
>
> Thank you all!
> Alex
next prev parent reply other threads:[~2020-03-06 4:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200306025041.rERhvnYmB%akpm@linux-foundation.org>
2020-03-06 3:32 ` [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch removed from -mm tree Qian Cai
2020-03-06 3:38 ` Matthew Wilcox
2020-03-06 3:50 ` Qian Cai
2020-03-06 4:17 ` Hugh Dickins
2020-03-06 4:42 ` Alex Shi
2020-03-06 4:46 ` Qian Cai [this message]
2020-03-06 13:30 ` Alex Shi
2020-03-06 14:54 ` Johannes Weiner
2020-03-06 9:04 ` Alex Shi
2020-03-06 11:58 ` Alex Shi
2020-03-07 2:27 ` Qian Cai
2020-03-07 3:26 ` Alex Shi
2020-03-07 3:31 ` 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=1E0DE356-9F9B-4E00-9F53-85E2FED99CF2@lca.pw \
--to=cai@lca.pw \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=daniel.m.jordan@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill@shutemov.name \
--cc=kravetz@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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).