From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0A46C433EF for ; Thu, 7 Apr 2022 08:31:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243069AbiDGId1 (ORCPT ); Thu, 7 Apr 2022 04:33:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243045AbiDGIdZ (ORCPT ); Thu, 7 Apr 2022 04:33:25 -0400 Received: from gandalf.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3C6511728B6; Thu, 7 Apr 2022 01:31:23 -0700 (PDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4KYvjY6Rg9z4xZ3; Thu, 7 Apr 2022 18:31:13 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canb.auug.org.au; s=201702; t=1649320279; bh=sG3iKOR7eX1exkY5m5McEH06+OHvCNrCCmrkW2t6mPw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Tb6aWuQnBAXP6tq8BkXFqkJ9qXQ7j+Ssg31lMCAA3ftBlIlAfTA4TlFldTXWjJhj6 UiGPVJxV44LH3mYCfXlb9U7LmX35v9CXzzTK/VHPEgu6Q+HiZmkLo71wAv1z6kKByR lwo5svIrEXZX/6v6J94Lix58+6g2sIbQOheKlI7OwKTSoOx57H8wcVrx/5nPf9vY0x cGOsbRqFmeWeNMeL5U+47uKhAdFImXVQn7FGHeMwNVN/aT9uqcNRwr3F8176aJpGVY LaHvSQJjXveD6JVjgLYF6iiFtWdeOrrLJHQAFzDLx+Op/LIx/Xn0+NnLkZga29q5Gs TLp1u7PGIAHiw== Date: Thu, 7 Apr 2022 18:31:12 +1000 From: Stephen Rothwell To: Yu Zhao Cc: Linux-MM , Andi Kleen , Andrew Morton , Aneesh Kumar , Barry Song <21cnbao@gmail.com>, Catalin Marinas , Dave Hansen , Hillf Danton , Jens Axboe , Jesse Barnes , Johannes Weiner , Jonathan Corbet , Linus Torvalds , Matthew Wilcox , Mel Gorman , Michael Larabel , Michal Hocko , Mike Rapoport , Rik van Riel , Vlastimil Babka , Will Deacon , Ying Huang , Linux ARM , "open list:DOCUMENTATION" , linux-kernel , Kernel Page Reclaim v2 , "the arch/x86 maintainers" Subject: Re: [PATCH v10 00/14] Multi-Gen LRU Framework Message-ID: <20220407183112.2cb5b627@canb.auug.org.au> In-Reply-To: References: <20220407031525.2368067-1-yuzhao@google.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/vv2ccmDjANVQ_zxEAVutc2L"; protocol="application/pgp-signature"; micalg=pgp-sha256 Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org --Sig_/vv2ccmDjANVQ_zxEAVutc2L Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Yu, On Wed, 6 Apr 2022 21:24:27 -0600 Yu Zhao wrote: > > Can you please include this patchset in linux-next? Git repo for you to f= etch: >=20 > https://linux-mm.googlesource.com/mglru for-linux-next I get a message saying "This repository is empty. Push to it to show branches and history." :-( > My goal is to get additional test coverage before I send a pull > request for 5.19 to Linus. Good idea :-) > I've explored all avenues, but ultimately I've failed to rally > substantial support from the MM stakeholders [1]. There are no pending > technical issues against this patchset [2]. What is more concerning > are the fundamental disagreements on priorities, methodologies, etc. > that are not specific to this patchset and have been hindering our > progress as a collective. (Cheers to the mutual dissatisfaction.) I have not been following the discussion as I am not an mm person, but this is not a good sign. > While we plan to discuss those issues during the LSFMM next month, it > doesn't seem reasonable to leave this patchset hanging in the air, > since it has reached its maturity a while ago and there are strong > demands from downstream kernels as well as a large user base. Thus I > sent that pull request to Linus a couple of weeks ago, implying that > he would have to make the final decision soon. >=20 > I hope this gives enough background about what's been going on with > this patchset. If you decide to take it and it causes you any > troubles, please feel free to yell at me. >=20 > Thanks! >=20 > [1] https://lore.kernel.org/r/20220104202227.2903605-1-yuzhao@google.com/ > [2] https://lore.kernel.org/r/20220326010003.3155137-1-yuzhao@google.com/ I had a look at those threads and I guess things are better that your comment above implies. So, a couple of questions: Have you done a trial merge with a current linux-next tree to see what sort of mess/pain we may already be in? Is it all stable enough now that it could be sent as a patch series for Andrew to include in mmotm (with perhaps just smallish followup patches)? --=20 Cheers, Stephen Rothwell --Sig_/vv2ccmDjANVQ_zxEAVutc2L Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmJOoVEACgkQAVBC80lX 0GzE3Qf5AQTCVeynkAsn3+qk9evNVsNw+dWxlovauW3+RjhUcon2308Q6aN7oSPw fex528YIkIZ5WBjpCvTqt2qy/wsUfN01Terj/MrmC1NVIWSVdQxQo1xydTpbwRym aKXyxU4rcp1o17/P65KZsISf0KXPXFKnLdPAKs5wEbgD6at5eohehdsGYCWk9hnX 1f/rEP51PEmxl9AE91SbpTvw3Mj5uKz282I3mUJiqQaIDPcNbPv6qM9RLKRYa9Kn IOdqR6+UvqVE0BLoi0Q3ikCuC7RI3wSuAsDlKhLL7QtlbRDjKbAT/qTxo408JScg pPI07lXejPErRWE6+HSo4yLiLW9+iQ== =mvXT -----END PGP SIGNATURE----- --Sig_/vv2ccmDjANVQ_zxEAVutc2L--