Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp2746907pxa; Tue, 25 Aug 2020 02:00:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzyptfzOxfdmM3YJqTMrDGJeZl3RbWTDRDAOad+5rP0uhTmgrITGpjJvPvjMTkfOrClr82+ X-Received: by 2002:a17:906:4047:: with SMTP id y7mr9212795ejj.21.1598346014342; Tue, 25 Aug 2020 02:00:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598346014; cv=none; d=google.com; s=arc-20160816; b=mmPTvcWhy8J12wOKVc49GwViSv96NEWayNFb6Lvl9DLjY3KfLItr632ESPw+v7lLsK 65HuvZWN/e7fqnoW9BKviv8dUyBByHXZi1vDMSeElZSI1EDMISfimId9lqDoZD7fhsDT vxL2ulSy8D8IJDyfuwX5h7xRjpbJ4M14AEG1s4LKVgEXkdcIsBLDYEG+49HMJzhj+xUT 3RVZp30wfQMJI3RMV6bclRNd36DFTMTPAdN1jqex2D7twl+8lsimyfZ8QvX3FL2AO4oZ 8Dlgz5wT5uU36lZfdMSe3KpAkG69FOCV1MAWxkOSOEvXJhERt6z6yL8Cft/KV4dsrm7R 4+nQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Fevfy98L+YVKFFcweFaoSROWiZIHrmtUENs7WzvvqGY=; b=J9dj13HFuay6d3IzF5rUFG4kmf20TQcWKi9qY9/a0KKBTAsD8ZijovVzjuIWw6kPyn TqfBNt60vNjvKc9OtZWB8NdPAXbzYAqloRq+lH0eTMEQH3arfxURsuDzQl9yqVUZ+eTQ 1O5CgSJy21U+07TXVm1o0V+wbS4xYX3JeKeoIu4sCcwgoQ69Ai+Gn+f7m8iwcNt3AO5H RSaz+/CirPY2Lkdc3RK2K97BO/Fnx2G14bSVxZiHbvfrnEK+cyI48V7X+c3JrRVUAxDG auzG+1i0WG0ZISHuPBG1z3ucRLosYG1nUt86KEeYfr4yv5qjZeWn5Z4Pt2mpIxWoLjFv NkrA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k23si3198748ejq.25.2020.08.25.01.59.51; Tue, 25 Aug 2020 02:00:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729367AbgHYHVi (ORCPT + 99 others); Tue, 25 Aug 2020 03:21:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:54050 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729277AbgHYHVi (ORCPT ); Tue, 25 Aug 2020 03:21:38 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 8A81FAE63; Tue, 25 Aug 2020 07:22:06 +0000 (UTC) Date: Tue, 25 Aug 2020 09:21:34 +0200 From: Michal Hocko To: Andrew Morton Cc: Alex Shi , mgorman@techsingularity.net, tj@kernel.org, hughd@google.com, khlebnikov@yandex-team.ru, daniel.m.jordan@oracle.com, willy@infradead.org, hannes@cmpxchg.org, lkp@intel.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, shakeelb@google.com, iamjoonsoo.kim@lge.com, richard.weiyang@gmail.com, kirill@shutemov.name, alexander.duyck@gmail.com, rong.a.chen@intel.com, vdavydov.dev@gmail.com, shy828301@gmail.com Subject: Re: [PATCH v18 00/32] per memcg lru_lock Message-ID: <20200825072134.GA22869@dhcp22.suse.cz> References: <1598273705-69124-1-git-send-email-alex.shi@linux.alibaba.com> <20200824114204.cc796ca182db95809dd70a47@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200824114204.cc796ca182db95809dd70a47@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 24-08-20 11:42:04, Andrew Morton wrote: > On Mon, 24 Aug 2020 20:54:33 +0800 Alex Shi wrote: > > > The new version which bases on v5.9-rc2. The first 6 patches was picked into > > linux-mm, and add patch 25-32 that do some further post optimization. > > 32 patches, version 18. That's quite heroic. I'm unsure whether I > should merge it up at this point - what do people think? This really needs a proper review. Unfortunately : 24 files changed, 646 insertions(+), 443 deletions(-) is quite an undertaking to review as well. Especially in a tricky code which is full of surprises. I do agree that per memcg locking looks like a nice feature but I do not see any pressing reason to merge it ASAP. The cover letter doesn't really describe any pressing usecase that cannot really live without this being merged. I am fully aware of my dept to review but I simply cannot find enough time to sit on it and think it through to have a meaningful feedback at this moment. > > Following Daniel Jordan's suggestion, I have run 208 'dd' with on 104 > > containers on a 2s * 26cores * HT box with a modefied case: > > https://git.kernel.org/pub/scm/linux/kernel/git/wfg/vm-scalability.git/tree/case-lru-file-readtwice > > With this patchset, the readtwice performance increased about 80% > > in concurrent containers. > > That's rather a slight amount of performance testing for a huge > performance patchset! Is more detailed testing planned? Agreed! This needs much better testing coverage. -- Michal Hocko SUSE Labs