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 37241C433FE for ; Thu, 7 Apr 2022 09:41:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237042AbiDGJno (ORCPT ); Thu, 7 Apr 2022 05:43:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50900 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234890AbiDGJn1 (ORCPT ); Thu, 7 Apr 2022 05:43:27 -0400 Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E4B3AE9978 for ; Thu, 7 Apr 2022 02:41:27 -0700 (PDT) Received: by mail-vs1-xe31.google.com with SMTP id i186so3071471vsc.9 for ; Thu, 07 Apr 2022 02:41:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z7zJJ3dVoUtJLqxQIGYbqRajy422RRa0RyqoMndHc4s=; b=JkMq8F+3HtqO81NBb1mkbEohTJ6kSw94E2HbJldlJImgri78wn/U3VLQp5g3pt4vwu Oe3axNLegualBV2dfsFabBMvpDHS11gaY2Qw29J7JTL8Oa104iEKUtNyybRoQJ2sZ65U HyDQybd4LaFvI+CJyrfhdiDxb7yqzjdImxYove6PUfT25p/HG9P3Pmf5Evcb0ODwU+jS V/WwpuTXm4hM1VYORFumSwU3lEzCPKr+NA2oGfAc0U7FiEiP7MgWSFP9EzlHssjpgL+P pm+hgBbIrLJFdgk1fC7jOMsY4OnDdgy+B2/j8ina8ycxYobiXaeWtaw0biULRtVwzBDw 3WKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z7zJJ3dVoUtJLqxQIGYbqRajy422RRa0RyqoMndHc4s=; b=bX2iztkQz1bTOnoAnkFlXdgRCSIdObHfzyRQ1nlrqEiIZpWhNKwn70VeAqNozAIhQW qztgjNy7VWAMzaLbVXaEOKfCMMTSiO4pVXmo44esRaalDV5LAh9tYHN0IL4NXO9zhGAO ZRBKSQDPevUhnglsJMlWPKB8gBX3HpsniNJD3Oi4LPMXFFJ0Ew3tKjAB7GCIlIIkg2Ky 2oF3+IkoSnVc5UPf4GWobIyi5EkZ1cd520o5SvYiR4YO+viO6TvgGv0dkrhYQgZnJA2u Gifeng2rJ2/Y6OP6kIrt5xD7m/J/DqDwmjNsMLUBiYtcLZzurwZGWNZhxKbUXyJ02nDT BG6w== X-Gm-Message-State: AOAM531zgv/XzuUhXqI7llwTdyzQDjkghHEniJkn5stS0a5afNAzUP/w Wb+eIftQ9t4fyNRVg57jRZ4wZ1uNVKtDhAmkRB2y8g== X-Google-Smtp-Source: ABdhPJznbN/TbVfynuU05EKXVCH2yRC1wZVWoNNxhWpZNDl5eLfDeRuTca6WXDt0On9YhbPtyNMup3nQhkj5pv50cFM= X-Received: by 2002:a05:6102:3753:b0:325:c20e:4b1c with SMTP id u19-20020a056102375300b00325c20e4b1cmr4264725vst.84.1649324486928; Thu, 07 Apr 2022 02:41:26 -0700 (PDT) MIME-Version: 1.0 References: <20220407031525.2368067-1-yuzhao@google.com> <20220407183112.2cb5b627@canb.auug.org.au> In-Reply-To: <20220407183112.2cb5b627@canb.auug.org.au> From: Yu Zhao Date: Thu, 7 Apr 2022 03:41:15 -0600 Message-ID: Subject: Re: [PATCH v10 00/14] Multi-Gen LRU Framework To: Stephen Rothwell 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" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 7, 2022 at 2:31 AM Stephen Rothwell wrote: > > 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 fetch: > > > > 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." :-( Sorry about this. It should work now. > > 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. > > > > 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. > > > > Thanks! > > > > [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? Yes, the repo I prepared for you is based on the latest linux-next. There shouldn't be any conflicts. > 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)? Yes, on multiple occasions, e.g., [1][2][3], I've claimed this patchset has an unprecedented test coverage and nobody has proven otherwise so far. Andrew suggested a cycle in linux-next [4]. So here we are :) [1] https://lore.kernel.org/all/YdSuSHa%2FVjl6bPkg@google.com/ [2] https://lore.kernel.org/r/YdiKVJlClB3h1Kmg@google.com/ [3] https://lore.kernel.org/r/YgR+MfXjpg82QyBT@google.com/ [4] https://lore.kernel.org/r/20220326134928.ad739eeecd5d0855dbdc6257@linux-foundation.org/ 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3875AC433F5 for ; Thu, 7 Apr 2022 09:56:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=FAvw229UZuinYeBbS2Ae3bEBqMdOKi6t1BBPx1KCRCU=; b=IRuk5C9cngdndp 3CHqanqLa3c/3gdKOevofVFYEotxt2+MGnWZzL59Bjavy2bjcQyi5GZREGXR05N8k4HUdiUtUjgcX u8MfkACq1ss3PkMMSYr59+mTtYu9VCj8p5H7/ymCjZfkmUI5D8FyjrtytqoQBII2UMXB49gvQLkQ8 xR8Oux2UfRYXAfCY5IkBdDCMwYdKtjq51yyXjLLpxAL4FDRToI6Z8xMPE5sjzXPi9aJikSKPSIyDX 1u8kMTk++AIgG06F1mGKugwv5Gb6/Hi2hNnBvb4y52P8sl4LpcR/zmuSqxj16xWRZfQXRVFppTfz1 UX3Xu1O/7qfU0aGjIruA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncOr0-00B2fm-VG; Thu, 07 Apr 2022 09:55:03 +0000 Received: from mail-vs1-xe2d.google.com ([2607:f8b0:4864:20::e2d]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ncOds-00AwwA-UR for linux-arm-kernel@lists.infradead.org; Thu, 07 Apr 2022 09:41:31 +0000 Received: by mail-vs1-xe2d.google.com with SMTP id v9so559758vss.10 for ; Thu, 07 Apr 2022 02:41:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z7zJJ3dVoUtJLqxQIGYbqRajy422RRa0RyqoMndHc4s=; b=JkMq8F+3HtqO81NBb1mkbEohTJ6kSw94E2HbJldlJImgri78wn/U3VLQp5g3pt4vwu Oe3axNLegualBV2dfsFabBMvpDHS11gaY2Qw29J7JTL8Oa104iEKUtNyybRoQJ2sZ65U HyDQybd4LaFvI+CJyrfhdiDxb7yqzjdImxYove6PUfT25p/HG9P3Pmf5Evcb0ODwU+jS V/WwpuTXm4hM1VYORFumSwU3lEzCPKr+NA2oGfAc0U7FiEiP7MgWSFP9EzlHssjpgL+P pm+hgBbIrLJFdgk1fC7jOMsY4OnDdgy+B2/j8ina8ycxYobiXaeWtaw0biULRtVwzBDw 3WKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z7zJJ3dVoUtJLqxQIGYbqRajy422RRa0RyqoMndHc4s=; b=DLcRvEBqBepdmK8jJB6aMf94dc5bwi6cHqLjQa+B2Q/54NapaXCB53BWpC7A0UFth6 y/izNY8RePYjt74ATG+cmp+61aQ5sqbL5BXtRevJq4dAuDBuJ7YNuXIuPMF05HRKAMMA PqtEBWsmFTVBMw2UgAha5pdDsqYUUChhG+Khj7e5MyQ3ftT6p2nGAezOgW00ufWKg0yi TW2qi2LHtf2WvdVewuqZo3qCPfyEaoMi0ri8J8YsGDa5jLkjVtz6OWb9CsQnvoaGm2+j Hp2MtABIIR8754LfZap9Ncdoh5jYhBY/kUtpiQKdY7Tz5WKrF6qgdOzScZKbc8xh2qcK NYrw== X-Gm-Message-State: AOAM531uqk9EQs1xSgTFMIKjb/EIUsQM09IdooxLHwV50IFOBcGDoXM+ dlAVnMNRDvctiGS/U/+890meGBZ5QrhTQ+M+n8NRoA== X-Google-Smtp-Source: ABdhPJznbN/TbVfynuU05EKXVCH2yRC1wZVWoNNxhWpZNDl5eLfDeRuTca6WXDt0On9YhbPtyNMup3nQhkj5pv50cFM= X-Received: by 2002:a05:6102:3753:b0:325:c20e:4b1c with SMTP id u19-20020a056102375300b00325c20e4b1cmr4264725vst.84.1649324486928; Thu, 07 Apr 2022 02:41:26 -0700 (PDT) MIME-Version: 1.0 References: <20220407031525.2368067-1-yuzhao@google.com> <20220407183112.2cb5b627@canb.auug.org.au> In-Reply-To: <20220407183112.2cb5b627@canb.auug.org.au> From: Yu Zhao Date: Thu, 7 Apr 2022 03:41:15 -0600 Message-ID: Subject: Re: [PATCH v10 00/14] Multi-Gen LRU Framework To: Stephen Rothwell 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" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220407_024129_035740_BDB77DF8 X-CRM114-Status: GOOD ( 36.75 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Apr 7, 2022 at 2:31 AM Stephen Rothwell wrote: > > 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 fetch: > > > > 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." :-( Sorry about this. It should work now. > > 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. > > > > 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. > > > > Thanks! > > > > [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? Yes, the repo I prepared for you is based on the latest linux-next. There shouldn't be any conflicts. > 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)? Yes, on multiple occasions, e.g., [1][2][3], I've claimed this patchset has an unprecedented test coverage and nobody has proven otherwise so far. Andrew suggested a cycle in linux-next [4]. So here we are :) [1] https://lore.kernel.org/all/YdSuSHa%2FVjl6bPkg@google.com/ [2] https://lore.kernel.org/r/YdiKVJlClB3h1Kmg@google.com/ [3] https://lore.kernel.org/r/YgR+MfXjpg82QyBT@google.com/ [4] https://lore.kernel.org/r/20220326134928.ad739eeecd5d0855dbdc6257@linux-foundation.org/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel