From patchwork Mon Nov 27 23:45:54 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Nhat Pham X-Patchwork-Id: 17179 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:ce62:0:b0:403:3b70:6f57 with SMTP id o2csp3550661vqx; Mon, 27 Nov 2023 15:46:12 -0800 (PST) X-Google-Smtp-Source: AGHT+IG04N3686phaDrpSqX5tKeYqU5hAR7OPPOaYffw7eK8kn7ajiFg77sRxE16P2G1QgnoiBBS X-Received: by 2002:a17:902:dac1:b0:1cf:edd5:f783 with SMTP id q1-20020a170902dac100b001cfedd5f783mr1763762plx.15.1701128772136; Mon, 27 Nov 2023 15:46:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701128772; cv=none; d=google.com; s=arc-20160816; b=SSnDiQE7cz4Hum27DmLKNxUMgHDBIvwjLilq/+0Gu34Nwz/hQQF1NpdX2eYlgvaNCQ /4jxkEQhnxhRuShaIAHUcvLQXjHzwsxNVbXnug81AMRg3Kor73kSK8n0OXwOwWO11Of0 7yOUpM6eWnLvwt22/tXNxeeGjCmD0LDs1OqSoohimwUaZwtdxiiTTVLSY97GZjtgVb1o OP2TveOpDwqyRiRHLJQIFvgeIbPyL6i8qVRmXxY3jjuigg4mvVEJ1kHOKYmqdI2uOFaj pR4fsLljM0o2yIGSOgjbUPWKNjIML7n437KIVwXMPnsI79O50+JEIbyV+ljCfPUIAV77 8Icg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=0naXIH0JGObfzirOc6Nz1+BDeP5C+xEUqfta7BLJ2ro=; fh=5ynFD2G6LA0fdRuAOSZxbBxHoIIG4U3xrwbnkupZs28=; b=cAGZ5YUojwZaJczj22m88DlZS9k+0oA4ILOSdFNwpd8iZU0bvyk0+iQr8KXU6lLirZ O7Ai6YZEpWIR+QSLh47468yNYu53E7mo/nEqdxjI8AH1Gv3YNNMBQxOH/FMxZOOXNmzH oXG5e6LLSLg7qMKXqeRFrtufSra54hb0T+7sMvy5RPSAb80EloVcIRPfys8nVrdJK/cs UELc9jVkXi4Klo3kdhSrfg6wZ43YvTnLqN3ROlN+/IrkpQtcB20FeRBYxojTUnkNIyL3 R9DQrCA5KIfJxKaEKtp4ceIyvFM1fH5PKs9v9zqO+BxfQ6sCuY0qEFlDmcODk8r4Gm+U 6x8g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=MENJJqiM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from morse.vger.email (morse.vger.email. [23.128.96.31]) by mx.google.com with ESMTPS id p3-20020a17090adf8300b0028076e86368si11012285pjv.144.2023.11.27.15.46.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Nov 2023 15:46:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20230601 header.b=MENJJqiM; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by morse.vger.email (Postfix) with ESMTP id E007B811216D; Mon, 27 Nov 2023 15:46:05 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at morse.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230510AbjK0Xp5 (ORCPT + 99 others); Mon, 27 Nov 2023 18:45:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35498 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229821AbjK0Xpz (ORCPT ); Mon, 27 Nov 2023 18:45:55 -0500 Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 91337187; Mon, 27 Nov 2023 15:46:01 -0800 (PST) Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1cfbda041f3so18615905ad.2; Mon, 27 Nov 2023 15:46:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701128761; x=1701733561; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=0naXIH0JGObfzirOc6Nz1+BDeP5C+xEUqfta7BLJ2ro=; b=MENJJqiM4GCznY2jincowkWiC2ussM3wPWwLZHmgqj6RKY0Xu4RkztypVtHY5YpBMP TBMhngz42ASS5EbG2CAyVpRGfZcUwmPWl8CNiUdracrdc/gnFj4EuIKrtv+dQ3UO80Jt ximg+5cf8BHlQe2Rjd7HlRhcoXlAvJL/L0Z32T8OxEgDoIvmuaYvOlUqVxnk79ScG149 +DkepOOCDBQhGC48azx9B1zJdVnSurIzxxF4Xgt9tWezMmNezp428RI9e1HzepzOXfco VtiDUOVstxYLY1/nCGyxd8IA+s0uOp85ga0c0cQJm6n2Sya5mkTI9jn8Y3b8UrE4qMvi C9kA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701128761; x=1701733561; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0naXIH0JGObfzirOc6Nz1+BDeP5C+xEUqfta7BLJ2ro=; b=q5XiS7XTAUG9BYpKBCsxTk34rQ0qNCY988kn7YhseALRu/G9Sr/sx4Q/EOmPD63wJA pdzqrpM33G2FpLby3YE9BbLq99Q6AxwdHxiDPU9H8K4jyq7cMC3NoRsVPJ6swIcgc/OR yCbTysqMVSDyo+uF4P11yZVaMfu8lv6eAhgffJKndNGPjgH9/4TNYoncp9OFcX1CU1yk fSEA7tnz/9vYd18EhPJ87U7wpSi2CmVgSoEUPZIFA9UQ1g8wgZ+upKlFoSMXwph+koN0 mBMIjP8HC0mUBGiQrnAqdP5YqyYkBzz4Ddz3uXIKDvn6teBXTIka3Sy9uCTaiKjNqLwm Zn4w== X-Gm-Message-State: AOJu0Ywn0YxyvVmXZ8P8Kt5neUEpe4HKg/ihktgVinQ465zrWmBWvdoy 4vWZdi1/vWCt6GbE4Txz0bY= X-Received: by 2002:a17:902:a707:b0:1cf:f1a0:c600 with SMTP id w7-20020a170902a70700b001cff1a0c600mr1039143plq.33.1701128760949; Mon, 27 Nov 2023 15:46:00 -0800 (PST) Received: from localhost (fwdproxy-prn-020.fbsv.net. [2a03:2880:ff:14::face:b00c]) by smtp.gmail.com with ESMTPSA id a9-20020a170902ee8900b001ca86a9caccsm8857868pld.228.2023.11.27.15.46.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Nov 2023 15:46:00 -0800 (PST) From: Nhat Pham To: akpm@linux-foundation.org Cc: hannes@cmpxchg.org, cerasuolodomenico@gmail.com, yosryahmed@google.com, sjenning@redhat.com, ddstreet@ieee.org, vitaly.wool@konsulko.com, mhocko@kernel.org, roman.gushchin@linux.dev, shakeelb@google.com, muchun.song@linux.dev, chrisl@kernel.org, linux-mm@kvack.org, kernel-team@meta.com, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org, shuah@kernel.org Subject: [PATCH v7 0/6] workload-specific and memory pressure-driven zswap writeback Date: Mon, 27 Nov 2023 15:45:54 -0800 Message-Id: <20231127234600.2971029-1-nphamcs@gmail.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on morse.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (morse.vger.email [0.0.0.0]); Mon, 27 Nov 2023 15:46:06 -0800 (PST) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1783747144755868600 X-GMAIL-MSGID: 1783762803801406049 Changelog: v7: * Added the mem_cgroup_iter_online() function to the API for the new behavior (suggested by Andrew Morton) (patch 2) * Fixed a missing list_lru_del -> list_lru_del_obj (patch 1) v6: * Rebase on top of latest mm-unstable. * Fix/improve the in-code documentation of the new list_lru manipulation functions (patch 1) v5: * Replace reference getting with an rcu_read_lock() section for zswap lru modifications (suggested by Yosry) * Add a new prep patch that allows mem_cgroup_iter() to return online cgroup. * Add a callback that updates pool->next_shrink when the cgroup is offlined (suggested by Yosry Ahmed, Johannes Weiner) v4: * Rename list_lru_add to list_lru_add_obj and __list_lru_add to list_lru_add (patch 1) (suggested by Johannes Weiner and Yosry Ahmed) * Some cleanups on the memcg aware LRU patch (patch 2) (suggested by Yosry Ahmed) * Use event interface for the new per-cgroup writeback counters. (patch 3) (suggested by Yosry Ahmed) * Abstract zswap's lruvec states and handling into zswap_lruvec_state (patch 5) (suggested by Yosry Ahmed) v3: * Add a patch to export per-cgroup zswap writeback counters * Add a patch to update zswap's kselftest * Separate the new list_lru functions into its own prep patch * Do not start from the top of the hierarchy when encounter a memcg that is not online for the global limit zswap writeback (patch 2) (suggested by Yosry Ahmed) * Do not remove the swap entry from list_lru in __read_swapcache_async() (patch 2) (suggested by Yosry Ahmed) * Removed a redundant zswap pool getting (patch 2) (reported by Ryan Roberts) * Use atomic for the nr_zswap_protected (instead of lruvec's lock) (patch 5) (suggested by Yosry Ahmed) * Remove the per-cgroup zswap shrinker knob (patch 5) (suggested by Yosry Ahmed) v2: * Fix loongarch compiler errors * Use pool stats instead of memcg stats when !CONFIG_MEMCG_KEM There are currently several issues with zswap writeback: 1. There is only a single global LRU for zswap, making it impossible to perform worload-specific shrinking - an memcg under memory pressure cannot determine which pages in the pool it owns, and often ends up writing pages from other memcgs. This issue has been previously observed in practice and mitigated by simply disabling memcg-initiated shrinking: https://lore.kernel.org/all/20230530232435.3097106-1-nphamcs@gmail.com/T/#u But this solution leaves a lot to be desired, as we still do not have an avenue for an memcg to free up its own memory locked up in the zswap pool. 2. We only shrink the zswap pool when the user-defined limit is hit. This means that if we set the limit too high, cold data that are unlikely to be used again will reside in the pool, wasting precious memory. It is hard to predict how much zswap space will be needed ahead of time, as this depends on the workload (specifically, on factors such as memory access patterns and compressibility of the memory pages). This patch series solves these issues by separating the global zswap LRU into per-memcg and per-NUMA LRUs, and performs workload-specific (i.e memcg- and NUMA-aware) zswap writeback under memory pressure. The new shrinker does not have any parameter that must be tuned by the user, and can be opted in or out on a per-memcg basis. As a proof of concept, we ran the following synthetic benchmark: build the linux kernel in a memory-limited cgroup, and allocate some cold data in tmpfs to see if the shrinker could write them out and improved the overall performance. Depending on the amount of cold data generated, we observe from 14% to 35% reduction in kernel CPU time used in the kernel builds. Domenico Cerasuolo (3): zswap: make shrinking memcg-aware mm: memcg: add per-memcg zswap writeback stat selftests: cgroup: update per-memcg zswap writeback selftest Nhat Pham (3): list_lru: allows explicit memcg and NUMA node selection memcontrol: add a new function to traverse online-only memcg hierarchy zswap: shrinks zswap pool based on memory pressure Documentation/admin-guide/mm/zswap.rst | 7 + drivers/android/binder_alloc.c | 7 +- fs/dcache.c | 8 +- fs/gfs2/quota.c | 6 +- fs/inode.c | 4 +- fs/nfs/nfs42xattr.c | 8 +- fs/nfsd/filecache.c | 4 +- fs/xfs/xfs_buf.c | 6 +- fs/xfs/xfs_dquot.c | 2 +- fs/xfs/xfs_qm.c | 2 +- include/linux/list_lru.h | 54 ++- include/linux/memcontrol.h | 18 + include/linux/mmzone.h | 2 + include/linux/vm_event_item.h | 1 + include/linux/zswap.h | 27 +- mm/list_lru.c | 48 ++- mm/memcontrol.c | 32 +- mm/mmzone.c | 1 + mm/swap.h | 3 +- mm/swap_state.c | 26 +- mm/vmstat.c | 1 + mm/workingset.c | 4 +- mm/zswap.c | 426 +++++++++++++++++--- tools/testing/selftests/cgroup/test_zswap.c | 74 ++-- 24 files changed, 641 insertions(+), 130 deletions(-) base-commit: 5cdba94229e58a39ca389ad99763af29e6b0c5a5 Acked-by: Johannes Weiner Tested-by: Bagas Sanjaya