From: Michal Hocko <mhocko@suse.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: "David Hildenbrand" <david@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Yu Zhao" <yuzhao@google.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andi Kleen" <ak@linux.intel.com>,
"Aneesh Kumar" <aneesh.kumar@linux.ibm.com>,
"Barry Song" <baohua@kernel.org>,
"Brian Geffon" <bgeffon@google.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Daniel Byrne" <djbyrne@mtu.edu>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Donald Carr" <d@chaos-reins.com>,
"Hillf Danton" <hdanton@sina.com>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
"Jan Alexander Steffens" <heftig@archlinux.org>,
"Jens Axboe" <axboe@kernel.dk>,
"Jesse Barnes" <jsbarnes@google.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Konstantin Kharlamov" <Hi-Angel@yandex.ru>,
"Mel Gorman" <mgorman@suse.de>,
"Michael Larabel" <Michael@michaellarabel.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Oleksandr Natalenko" <oleksandr@natalenko.name>,
"Rik van Riel" <riel@surriel.com>,
"Shuang Zhai" <szhai2@cs.rochester.edu>,
"Sofia Trinh" <sofia.trinh@edi.works>,
"Steven Barrett" <steven@liquorix.net>,
"Suleiman Souhlal" <suleiman@google.com>,
"Vaibhav Jain" <vaibhav@linux.ibm.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Will Deacon" <will@kernel.org>,
"Ying Huang" <ying.huang@intel.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
"Kernel Page Reclaim v2" <page-reclaim@google.com>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [page-reclaim] Re: [GIT PULL] Multi-gen LRU for 5.18-rc1
Date: Mon, 28 Mar 2022 16:27:27 +0200 [thread overview]
Message-ID: <YkHFz1f+s8+b5Qws@dhcp22.suse.cz> (raw)
In-Reply-To: <YkG7mD8kT0uAk3Iy@casper.infradead.org>
On Mon 28-03-22 14:43:52, Matthew Wilcox wrote:
> 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.
This is not the first time this has been brought up over years. We have
discussed the existing workflow at the LSFMM two years ago without a
larger consensus. I believe we want/need to resurrect those discussions
again. IMHO the existing workflow is more and more hitting its limits
so we should really think about a long term solution.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2022-03-28 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 1:00 Yu Zhao
2022-03-26 1:07 ` Linus Torvalds
2022-03-26 1:16 ` [page-reclaim] " Yu Zhao
2022-03-26 20:27 ` Linus Torvalds
2022-03-26 20:53 ` Yu Zhao
2022-03-26 20:49 ` Andrew Morton
2022-03-26 21:03 ` Yu Zhao
2022-03-28 12:29 ` David Hildenbrand
2022-03-28 13:43 ` Matthew Wilcox
2022-03-28 13:47 ` David Hildenbrand
2022-03-28 14:27 ` Michal Hocko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YkHFz1f+s8+b5Qws@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=Hi-Angel@yandex.ru \
--cc=Michael@michaellarabel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=baohua@kernel.org \
--cc=bgeffon@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=d@chaos-reins.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=djbyrne@mtu.edu \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=heftig@archlinux.org \
--cc=holger@applied-asynchrony.com \
--cc=jsbarnes@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=oleksandr@natalenko.name \
--cc=page-reclaim@google.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=sofia.trinh@edi.works \
--cc=steven@liquorix.net \
--cc=suleiman@google.com \
--cc=szhai2@cs.rochester.edu \
--cc=torvalds@linux-foundation.org \
--cc=vaibhav@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox