[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200604150539.GA322130@cmpxchg.org>
Date: Thu, 4 Jun 2020 11:05:39 -0400
From: Johannes Weiner <hannes@...xchg.org>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Joonsoo Kim <js1304@...il.com>,
Linux Memory Management List <linux-mm@...ck.org>,
Rik van Riel <riel@...riel.com>,
Minchan Kim <minchan.kim@...il.com>,
Michal Hocko <mhocko@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
LKML <linux-kernel@...r.kernel.org>, kernel-team@...com
Subject: Re: [PATCH 05/14] mm: workingset: let cache workingset challenge anon
On Thu, Jun 04, 2020 at 03:35:27PM +0200, Vlastimil Babka wrote:
> On 6/1/20 10:44 PM, Johannes Weiner wrote:
> > From a8faceabc1454dfd878caee2a8422493d937a394 Mon Sep 17 00:00:00 2001
> > From: Johannes Weiner <hannes@...xchg.org>
> > Date: Mon, 1 Jun 2020 14:04:09 -0400
> > Subject: [PATCH] mm: workingset: let cache workingset challenge anon fix
>
> Looks like the whole series is now in mainline (that was quick!) without this
> followup? As such it won't be squashed so perhaps the subject should be more
> "standalone" now, description referencing commit 34e58cac6d8f ("mm: workingset:
> let cache workingset challenge anon"), possibly with Fixes: tag etc...
Yep, I'll send a stand-alone version of this. It was a bit fat to get
squashed last minute anyway, and I don't mind having a bit of extra
time to quantify the actual impact of this delta.
Thanks Vlastimil!
Powered by blists - more mailing lists