[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9ac9c8c-15c1-8365-5c39-285c6d7b07a6@linux.alibaba.com>
Date: Wed, 21 Aug 2019 10:00:33 +0800
From: Alex Shi <alex.shi@...ux.alibaba.com>
To: Hugh Dickins <hughd@...gle.com>, Michal Hocko <mhocko@...nel.org>
Cc: Cgroups <cgroups@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux MM <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...hsingularity.net>,
Tejun Heo <tj@...nel.org>, Shakeel Butt <shakeelb@...gle.com>,
Yu Zhao <yuzhao@...gle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>
Subject: Re: [PATCH 00/14] per memcg lru_lock
在 2019/8/21 上午2:24, Hugh Dickins 写道:
> I'll set aside what I'm doing, and switch to rebasing ours to v5.3-rc
> and/or mmotm. Then compare with what Alex has, to see if there's any
> good reason to prefer one to the other: if no good reason to prefer ours,
> I doubt we shall bother to repost, but just use it as basis for helping
> to review or improve Alex's.
For your review, my patchset are pretty straight and simple. It just use per lruvec lru_lock to replace necessary pgdat lru_lock. just this.
We could talk more after I back to work. :)
Thanks alot!
Alex
Powered by blists - more mailing lists