Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp2839103pxb; Sun, 15 Nov 2020 20:34:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJzE3W0foVZRBWCQ1zbdYlrVr++sMmTL4WBWgSO3jFKaEmSbkfKhi9fgYWwUOHg12eF3EqNO X-Received: by 2002:a17:906:a444:: with SMTP id cb4mr13401974ejb.416.1605501285979; Sun, 15 Nov 2020 20:34:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605501285; cv=none; d=google.com; s=arc-20160816; b=NEp6CvMtdJ4AOIuO8FdpkRtRWMqdOCm/hJu/gf4BEEiikKPo2KlCTgdQSWBU8VApvV SArpS5EOFhcMMZ+g20tiigYkfLksQ0zmQcmPvn10tXpNvEWvDCuByxNk5cn5yDzPFD+j JnIx7f1tgWVYI+Lbe+h0j3tQnr+zSEstix5mlXBg9ODnqButXsDzZwET3HP4SVs7H9E2 5aXY+obsk226OWLBx4GWDz13dUczTRf+fQDPE0iC5zJthUayoCHdaq5ta033OK9aJv+Q QOiTRmjs2S3UTnG+SPG+OZmbrDMOZItEeQ2uk7Mi0zWv2NAo0TkXXoWMI9BJPzJspfbY 7n/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:references:to:from:subject; bh=XfLacTvVsUIPecPQzO0dFGfYeB3vbydbEwNaJzyv3qk=; b=rrZbo/vQG/wPjh9a4WgOVNynwHOBTawsa9s8c97vn1AGSj06hIjHdzgWCzDMbNW7Kg WAXDFr6ELNPhNNwd/awIrsrQYVdtHc4/BtTIWm5WBl9m8ClhXik2LJ/L7B7q/Amii87P M4DNjjGxWfySgwrBFUiHIdDAbHjo90soQRgfhOwLa11x+QBhVjpD6cY54m8WK4U7ungs Vf5FJXmE4bnzlQ8znnJiYHpgX/1rHTVnjiD9Zj/HxQAzVSOSlRJVZw2Bg0t1Nm33Xl/j K0bB4BxMCwcVK9zrN6/LX3m7/qqZg/ny5lxo9LB8XSiHyRiEmczX7tIMNcNEFHlj7udC zhoA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g10si2031425edu.349.2020.11.15.20.34.23; Sun, 15 Nov 2020 20:34:45 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726743AbgKPDrE (ORCPT + 99 others); Sun, 15 Nov 2020 22:47:04 -0500 Received: from out30-43.freemail.mail.aliyun.com ([115.124.30.43]:46418 "EHLO out30-43.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726732AbgKPDrE (ORCPT ); Sun, 15 Nov 2020 22:47:04 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R141e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=alimailimapcm10staff010182156082;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=21;SR=0;TI=SMTPD_---0UFSqqZF_1605498418; Received: from IT-FVFX43SYHV2H.local(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0UFSqqZF_1605498418) by smtp.aliyun-inc.com(127.0.0.1); Mon, 16 Nov 2020 11:46:59 +0800 Subject: Re: [PATCH v21 00/19] per memcg lru lock From: Alex Shi To: akpm@linux-foundation.org, 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, mhocko@suse.com, vdavydov.dev@gmail.com, shy828301@gmail.com References: <1604566549-62481-1-git-send-email-alex.shi@linux.alibaba.com> Message-ID: Date: Mon, 16 Nov 2020 11:45:51 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <1604566549-62481-1-git-send-email-alex.shi@linux.alibaba.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Andrew, With all patches are acked-by Hugh and Johannes, and full testing from LKP, is this patchset ready for more testing on linux-next? or anything still need be improved? Thanks Alex 在 2020/11/5 下午4:55, Alex Shi 写道: > This version rebase on next/master 20201104, with much of Johannes's > Acks and some changes according to Johannes comments. And add a new patch > v21-0006-mm-rmap-stop-store-reordering-issue-on-page-mapp.patch to support > v21-0007. > > This patchset followed 2 memcg VM_WARN_ON_ONCE_PAGE patches which were > added to -mm tree yesterday. > > Many thanks for line by line review by Hugh Dickins, Alexander Duyck and > Johannes Weiner. > > So now this patchset includes 3 parts: > 1, some code cleanup and minimum optimization as a preparation. > 2, use TestCleanPageLRU as page isolation's precondition. > 3, replace per node lru_lock with per memcg per node lru_lock. > > Current lru_lock is one for each of node, pgdat->lru_lock, that guard for > lru lists, but now we had moved the lru lists into memcg for long time. Still > using per node lru_lock is clearly unscalable, pages on each of memcgs have > to compete each others for a whole lru_lock. This patchset try to use per > lruvec/memcg lru_lock to repleace per node lru lock to guard lru lists, make > it scalable for memcgs and get performance gain. > > Currently lru_lock still guards both lru list and page's lru bit, that's ok. > but if we want to use specific lruvec lock on the page, we need to pin down > the page's lruvec/memcg during locking. Just taking lruvec lock first may be > undermined by the page's memcg charge/migration. To fix this problem, we could > take out the page's lru bit clear and use it as pin down action to block the > memcg changes. That's the reason for new atomic func TestClearPageLRU. > So now isolating a page need both actions: TestClearPageLRU and hold the > lru_lock. > > The typical usage of this is isolate_migratepages_block() in compaction.c > we have to take lru bit before lru lock, that serialized the page isolation > in memcg page charge/migration which will change page's lruvec and new > lru_lock in it. > > The above solution suggested by Johannes Weiner, and based on his new memcg > charge path, then have this patchset. (Hugh Dickins tested and contributed much > code from compaction fix to general code polish, thanks a lot!). > > Daniel Jordan's testing show 62% improvement on modified readtwice case > on his 2P * 10 core * 2 HT broadwell box on v18, which has no much different > with this v20. > https://lore.kernel.org/lkml/20200915165807.kpp7uhiw7l3loofu@ca-dmjordan1.us.oracle.com/ > > Thanks Hugh Dickins and Konstantin Khlebnikov, they both brought this > idea 8 years ago, and others who give comments as well: Daniel Jordan, > Mel Gorman, Shakeel Butt, Matthew Wilcox, Alexander Duyck etc. > > Thanks for Testing support from Intel 0day and Rong Chen, Fengguang Wu, > and Yun Wang. Hugh Dickins also shared his kbuild-swap case. Thanks!