Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp279777ybt; Fri, 19 Jun 2020 01:36:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyOZbCEiaMWi7ROqCMPOx99IbOvA0tRpsRJhq7OZeUyaNVjjwDrylCfPRa5LySKrwUFj8ih X-Received: by 2002:a17:906:370a:: with SMTP id d10mr2547710ejc.433.1592555805724; Fri, 19 Jun 2020 01:36:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592555805; cv=none; d=google.com; s=arc-20160816; b=kUp5qQmJTBtdWHhBqZ99q6OuqiQ/f6R6tb08i4fV/VaJ60+1s0iVW6lDNVL0/eCXyL CdR+3Pb29/PBhKU58i6sN3NkZz2oocKPbDCbvzn/kb37WBwImv0dPG0xDb8BBRl7yDK6 0clm7X+AX7OCdDiSgS9VS9Dvxu9byeB03WgdlNA4U57ZciybpnVywxBufSTO1lTq9YUT BF0Y2Ia32weXFGev7CTfuH/hwZcEZehojD5Wr/RiyV2nGatghyVw0U1N3rP8G/PujCgX vliiZDFgk3zRphvr9eqjAT6HUmvIkKS0NwvqzTMb9ZH32/PNExucu9IDoSzxICD+QsKA PQXg== 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=86L1n/kFbKcBOvrUpWp9t8IXZ3fmBFOra6dTLN53ocI=; b=NoyC/fYI4V3IwT5u+m4jwgEZQ2Gy2Izh7t7UUWbcAWSAJMen85yudRtS+SRebT4dVx 6u61W7m6+L7HxCfx0KYOLq3R0WzHPMletQkDcKce8vN0NaVbT87kid+tVlt/YOrIfdHg PqgYBjaE76eBp01NVuRsw6sIxcwZN85NjbHhmF6phMIf8fIyY4t0yFRxuR/GrnfVKEZM /+epQzLEVQm7Jmj+ItgvahXBvKbZBPeTUItW1ziTZrAo1Y0IcM/KdX2a6l+vtdMCmcyD KQfEt+EXEaCvbSb7EMpj0yEuCIBpdk54zl7LoI+G6FFGrwJEEJh3aAQDx4ZsHwfrrG7O 1cQg== 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 si25si3290264ejb.43.2020.06.19.01.36.23; Fri, 19 Jun 2020 01:36:45 -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 S1731561AbgFSIeX (ORCPT + 99 others); Fri, 19 Jun 2020 04:34:23 -0400 Received: from out30-44.freemail.mail.aliyun.com ([115.124.30.44]:41124 "EHLO out30-44.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731538AbgFSIeS (ORCPT ); Fri, 19 Jun 2020 04:34:18 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R191e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e01355;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=16;SR=0;TI=SMTPD_---0U01FUt1_1592555654; Received: from localhost(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0U01FUt1_1592555654) by smtp.aliyun-inc.com(127.0.0.1); Fri, 19 Jun 2020 16:34:14 +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 v13 00/18] per memcg lru lock Date: Fri, 19 Jun 2020 16:33:38 +0800 Message-Id: <1592555636-115095-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 linux-next, merged much suggestion from Hugh Dickins, from compaction fix to less TestClearPageLRU and comments reverse etc. Thank a lot, Hugh! 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 (16): 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/swap: fold vm event PGROTATED into pagevec_move_tail_fn mm/lru: introduce TestClearPageLRU mm/compaction: do page isolation first in compaction mm/mlock: reorder isolation sequence during munlock mm/swap: serialize memcg changes during pagevec_lru_move_fn 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 | 21 ++- Documentation/trace/events-kmem.rst | 2 +- Documentation/vm/unevictable-lru.rst | 22 +-- include/linux/compaction.h | 4 +- include/linux/memcontrol.h | 95 +++++++++++ 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 | 113 ++++++++----- mm/filemap.c | 4 +- mm/huge_memory.c | 54 +++++-- mm/memcontrol.c | 56 ++++++- mm/mlock.c | 93 +++++------ mm/mmzone.c | 1 + mm/page_alloc.c | 1 - mm/page_idle.c | 8 - mm/rmap.c | 4 +- mm/swap.c | 175 +++++++-------------- mm/swap_state.c | 5 +- mm/vmscan.c | 165 ++++++++++--------- mm/workingset.c | 4 +- 24 files changed, 500 insertions(+), 357 deletions(-) -- 1.8.3.1