Re: [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection

To: Roman Gushchin <guro@xxxxxx>
Subject: Re: [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection
From: Chris Down <chris@xxxxxxxxxxxxxx>
Date: Fri, 22 Mar 2019 23:51:20 +0000
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Johannes Weiner <hannes@xxxxxxxxxxx>, Michal Hocko <mhocko@xxxxxxxxxx>, Tejun Heo <tj@xxxxxxxxxx>, Dennis Zhou <dennis@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "cgroups@xxxxxxxxxxxxxxx" <cgroups@xxxxxxxxxxxxxxx>, "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, Kernel Team <Kernel-team@xxxxxx>
In-reply-to: <20190322224946.GA12527@chrisdown.name>
References: <20190228213050.GA28211@chrisdown.name> <20190322160307.GA3316@chrisdown.name> <20190322222907.GA17496@tower.DHCP.thefacebook.com> <20190322224946.GA12527@chrisdown.name>
User-agent: Mutt/1.11.4 (2019-03-13)

Chris Down writes:

Are you certain? If so, I don't see what you mean. This is how thecode looks in Linus' tree after the fixups:

Hmm, apparently this actually didn't go into Linus' tree yet, so yeah, seemsworth having as a fixup maybe indeed.

References:
- [PATCH] mm, memcg: Make scan aggression always exclude protection
  - From: Chris Down
- [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection
  - From: Chris Down
- Re: [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection
  - From: Roman Gushchin
- Re: [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection
  - From: Chris Down