[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkG7mD8kT0uAk3Iy@casper.infradead.org>
Date: Mon, 28 Mar 2022 14:43:52 +0100
From: Matthew Wilcox <willy@...radead.org>
To: David Hildenbrand <david@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Yu Zhao <yuzhao@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andi Kleen <ak@...ux.intel.com>,
Aneesh Kumar <aneesh.kumar@...ux.ibm.com>,
Barry Song <baohua@...nel.org>,
Brian Geffon <bgeffon@...gle.com>,
Catalin Marinas <catalin.marinas@....com>,
Daniel Byrne <djbyrne@....edu>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Donald Carr <d@...os-reins.com>,
Hillf Danton <hdanton@...a.com>,
Holger Hoffstätte
<holger@...lied-asynchrony.com>,
Jan Alexander Steffens <heftig@...hlinux.org>,
Jens Axboe <axboe@...nel.dk>,
Jesse Barnes <jsbarnes@...gle.com>,
Johannes Weiner <hannes@...xchg.org>,
Jonathan Corbet <corbet@....net>,
Konstantin Kharlamov <Hi-Angel@...dex.ru>,
Mel Gorman <mgorman@...e.de>,
Michael Larabel <Michael@...haellarabel.com>,
Michal Hocko <mhocko@...nel.org>,
Mike Rapoport <rppt@...nel.org>,
Oleksandr Natalenko <oleksandr@...alenko.name>,
Rik van Riel <riel@...riel.com>,
Shuang Zhai <szhai2@...rochester.edu>,
Sofia Trinh <sofia.trinh@....works>,
Steven Barrett <steven@...uorix.net>,
Suleiman Souhlal <suleiman@...gle.com>,
Vaibhav Jain <vaibhav@...ux.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>,
Will Deacon <will@...nel.org>,
Ying Huang <ying.huang@...el.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
Kernel Page Reclaim v2 <page-reclaim@...gle.com>,
the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [page-reclaim] Re: [GIT PULL] Multi-gen LRU for 5.18-rc1
On Mon, Mar 28, 2022 at 02:29:20PM +0200, David Hildenbrand wrote:
> I'd appreciate if we could merge most MM-related stuff through the -MM
> tree; it exists for a reason IMHO. Andrew, you usually have a very good
> feeling when something's ready to be merged upstream (sufficient review
> from relevant folks, sufficient exposure via -mm and -next, ...).
The problem is that the MM tree is completely unusable when patches going
in through other trees need to be based on it. The MM workflow clearly
works well for Andrew, but it doesn't work well for us as a community.
Fortunately folios is past that point now, but I fear that maple tree
will get to that point if it doesn't go in through Andrew's tree this
cycle, as it may have other users.
Powered by blists - more mailing lists