From: Matthew Wilcox <willy@infradead.org>
To: Qian Cai <cai@lca.pw>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
aarcange@redhat.com, Alex Shi <alex.shi@linux.alibaba.com>,
daniel.m.jordan@oracle.com, hannes@cmpxchg.org, hughd@google.com,
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
Subject: Re: [failures] mm-vmscan-remove-unnecessary-lruvec-adding.patch removed from -mm tree
Date: Thu, 5 Mar 2020 19:38:50 -0800 [thread overview]
Message-ID: <20200306033850.GO29971@bombadil.infradead.org> (raw)
In-Reply-To: <211632B1-2D6F-4BFA-A5A0-3030339D3D2A@lca.pw>
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…
See Hugh's message from a few minutes ago:
Subject: Re: [PATCH v9 00/21] per lruvec lru_lock for memcg
next prev parent reply other threads:[~2020-03-06 3:38 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 [this message]
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
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=20200306033850.GO29971@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=cai@lca.pw \
--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=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--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).