[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190322235120.GA31019@chrisdown.name>
Date: Fri, 22 Mar 2019 23:51:20 +0000
From: Chris Down <chris@...isdown.name>
To: Roman Gushchin <guro@...com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>, Tejun Heo <tj@...nel.org>,
Dennis Zhou <dennis@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Kernel Team <Kernel-team@...com>
Subject: Re: [PATCH REBASED] mm, memcg: Make scan aggression always exclude
protection
Chris Down writes:
>Are you certain? If so, I don't see what you mean. This is how the
>code looks in Linus' tree after the fixups:
Hmm, apparently this actually didn't go into Linus' tree yet, so yeah, seems
worth having as a fixup maybe indeed.
Powered by blists - more mailing lists