[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220426130603.2fa538088d10d38a740a0bdd@linux-foundation.org>
Date: Tue, 26 Apr 2022 13:06:03 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Liam Howlett <liam.howlett@...cle.com>
Cc: "maple-tree@...ts.infradead.org" <maple-tree@...ts.infradead.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Yu Zhao <yuzhao@...gle.com>
Subject: Re: [PATCH v8 00/70] Introducing the Maple Tree
On Tue, 26 Apr 2022 15:06:19 +0000 Liam Howlett <liam.howlett@...cle.com> wrote:
> Please replace the patches in your mglru-maple branch with this set. It should
> be a drop in replacement for my patch range with the fixes into these
> patches. Adding the preallocation to work around the fs-reclaim LOCKDEP
> issue caused enough changes to the patches to warrant a respin.
OK, thanks. I'll give these a bit of testing locally with a view to
having a run in -next soon.
It's all not looking very reviewed. Any thoughts on who we could
attempt to presuade to hep out here?
> The last patch on the branch is still needed to fix vmscan after mglru
> is applied. ee4b1fc24f30 "mm/vmscan: Use VMA_ITERATOR in
> get_next_vma()"
OK, someone please send that at me when the next rev of mglru surfaces?
Powered by blists - more mailing lists