Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1064738ybg; Wed, 10 Jun 2020 23:19:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzO+e6OiwI47VR0eP+uOKCc/wsyqHwOBVgA1z6Rzn922lVKBfmyq23MCpNzbhghyqD43udm X-Received: by 2002:a50:bf03:: with SMTP id f3mr5827459edk.368.1591856356423; Wed, 10 Jun 2020 23:19:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591856356; cv=none; d=google.com; s=arc-20160816; b=CGhOx2ECvG9oWqJJvxEpUJlBrVYH6PnTF2kyZ0eAOeIjT5IIrIIZxM2P8mFxWqW/ZW 9/apPXxx5kIB9lPdeupZ695ektRzt2nyMObA7n8Cw4Vz53A72LlmWAS1TT0O1uVj+k+L oIzANR+M2N+zeIv8we6WqAmzf4DXacsQmFIwsPleK06PiRHZV2Dfrg0nPzNnovfG5rHw bQb14P8Eq1D28GNlhAx1oGVIX1QjnoCfszWQA18ZXz000ZuqLwLrecSGCz8ucClS7jQ4 Udx38gtsTdJpaq5NuzhsJPeeLtAlOiq/0btYmTwUtmo6Beqn+v1MvkmzSG4VU8/w5zeq RgJw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:to:from; bh=t2/f/4IT8ST/1Ar7cmmrEUCK09ze9Yq1qlDd1h+fcsA=; b=VPo/u3vZWX7aqBeutKt08q/PTNCm7aAh13W50m+gt05T+z3U+ZPyTwjZFKAuDa0g3P bPGA637ZsdnOqCdVWeqNa3fYgPJdTVIyMRdUrctFTkQYj/aIZEHZz4h875rJETNVqoZA GKa5Pkww1yF9whhV1HecpDT9xVbCEiALN1gSmI6Buyyk2+JqliEEa4Z+JTnIciydiFXm W35rt/BUNhPVMgIEixphooUKAG+OlvGEpUq4Dpl3bBEYPe1HjL8Gct1OFuDHgSjXF7Um Za1NBiEq+UMAZZ299zMH949D04U2Utt3gD79uJLOT15Rr3kOUaxmPQUaUXVvGt0fz7kv fcKw== 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 dc20si1039107edb.75.2020.06.10.23.18.53; Wed, 10 Jun 2020 23:19:16 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726536AbgFKGRH (ORCPT + 99 others); Thu, 11 Jun 2020 02:17:07 -0400 Received: from out30-132.freemail.mail.aliyun.com ([115.124.30.132]:37037 "EHLO out30-132.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726462AbgFKGRH (ORCPT ); Thu, 11 Jun 2020 02:17:07 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R511e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01f04397;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=16;SR=0;TI=SMTPD_---0U.FKMxv_1591856220; Received: from localhost(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0U.FKMxv_1591856220) by smtp.aliyun-inc.com(127.0.0.1); Thu, 11 Jun 2020 14:17:00 +0800 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, yang.shi@linux.alibaba.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 Subject: [PATCH v12 00/16] per memcg lru lock Date: Thu, 11 Jun 2020 14:16:33 +0800 Message-Id: <1591856209-166869-1-git-send-email-alex.shi@linux.alibaba.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is a new version which bases on v5.8, only change mm/compaction.c since mm-compaction-avoid-vm_bug_onpageslab-in-page_mapcount.patch removed. Johannes Weiner has suggested: "So here is a crazy idea that may be worth exploring: Right now, pgdat->lru_lock protects both PageLRU *and* the lruvec's linked list. Can we make PageLRU atomic and use it to stabilize the lru_lock instead, and then use the lru_lock only serialize list operations? ..." With new memcg charge path and this solution, we could isolate LRU pages to exclusive visit them in compaction, page migration, reclaim, memcg move_accunt, huge page split etc scenarios while keeping pages' memcg stable. Then possible to change per node lru locking to per memcg lru locking. As to pagevec_lru_move_fn funcs, it would be safe to let pages remain on lru list, lru lock could guard them for list integrity. The 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 The 3rd part moves per node lru_lock into lruvec, thus bring a lru_lock for each of memcg per node. So on a large machine, each of memcg don't have to suffer from per node pgdat->lru_lock competition. They could go fast with their self lru_lock 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. 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 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! Alex Shi (14): mm/vmscan: remove unnecessary lruvec adding mm/page_idle: no unlikely double check for idle page counting mm/compaction: correct the comments of compact_defer_shift mm/compaction: rename compact_deferred as compact_should_defer mm/thp: move lru_add_page_tail func to huge_memory.c mm/thp: clean up lru_add_page_tail mm/thp: narrow lru locking mm/memcg: add debug checking in lock_page_memcg mm/lru: introduce TestClearPageLRU mm/compaction: do page isolation first in compaction mm/mlock: reorder isolation sequence during munlock mm/lru: replace pgdat lru_lock with lruvec lock mm/lru: introduce the relock_page_lruvec function mm/pgdat: remove pgdat lru_lock Hugh Dickins (2): mm/vmscan: use relock for move_pages_to_lru mm/lru: revise the comments of lru_lock Documentation/admin-guide/cgroup-v1/memcg_test.rst | 15 +- Documentation/admin-guide/cgroup-v1/memory.rst | 8 +- Documentation/trace/events-kmem.rst | 2 +- Documentation/vm/unevictable-lru.rst | 22 +-- include/linux/compaction.h | 4 +- include/linux/memcontrol.h | 92 +++++++++++ include/linux/mm_types.h | 2 +- include/linux/mmzone.h | 6 +- include/linux/page-flags.h | 1 + include/linux/swap.h | 4 +- include/trace/events/compaction.h | 2 +- mm/compaction.c | 96 +++++++----- mm/filemap.c | 4 +- mm/huge_memory.c | 51 +++++-- mm/memcontrol.c | 87 ++++++++++- mm/mlock.c | 93 ++++++------ mm/mmzone.c | 1 + mm/page_alloc.c | 1 - mm/page_idle.c | 8 - mm/rmap.c | 2 +- mm/swap.c | 112 ++++---------- mm/swap_state.c | 6 +- mm/vmscan.c | 168 +++++++++++---------- mm/workingset.c | 4 +- 24 files changed, 481 insertions(+), 310 deletions(-) -- 1.8.3.1