Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp6680115rwb; Mon, 5 Dec 2022 16:20:29 -0800 (PST) X-Google-Smtp-Source: AA0mqf7OJ90dSXnBIJaHKOLnDSjiWW9T75rlS5G5qXgebFLD7w9O+93c4V9rspIjKjxwrjM/wM5s X-Received: by 2002:a17:906:124d:b0:7ad:b822:d2e4 with SMTP id u13-20020a170906124d00b007adb822d2e4mr71415673eja.35.1670286029685; Mon, 05 Dec 2022 16:20:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670286029; cv=none; d=google.com; s=arc-20160816; b=VfcUN9rivubFqkRCbEQWAqHubuZISBD4FkNyb/OBZjihYk3CU+NbXn4N6JCE7I7jJW uNQTL/oKDdyulwcXJ3IL55baN0p3sQfatETa+uINMIk5CQwIJ7vKqfdpXpRu4NMBCZF2 vpZTgN5251x6oU74kdLNaC7KmBwyF4KBDOvaTWSZplfMtW6x+/3ZcFdzkP8eCY9X8m5N IsfYhz3IMEfMcfPQlUDE3VntrPXMyzisApC8jkxBUkeFbE+B0XVNXPm7cnCFPkYGdbmD NUQ1nfTDJ/WZ2pir1jPEkQ1RERz9iUEH8N5ix/f6/5Nip8HzX5mwEdInUxobk7571EtE dxaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=CN9j3kYVvyZ5N6wvjIbsfvlwhZyZism7lUmKxfBm3qo=; b=r6/e5UFDDXMHFVqNO2dj7ZAWCjXM7enmkp6i5HnKGYpMYu1wlJdjnBzUbzCg116FWu PEduacaD0Eu4lHQdqpPbP+dl2hkefhe6yY1ASZb0ZLKVirNQ27PsBQ7ANEQWy6Ohi67j vddF5WldVrUBppyPg5SdZrRSBer+H/j05G+ADTpfzRIM9lS1mbpsSkVl9envMxXLHi3D 9QNrK2d+F4N2jH/xbC+aKzmOybri8Sl5tF4Px/txzZ8vVjFw8hCYaq8KWhiG9XalRlr7 WXtA+h+XF6zmuNi8mmlFkcuRvwXrgEgzw/Pk2D9qs0DfqrNoGKaLlDBuxHoDVZ9rF+ad 6Qpg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=oGxMdcr+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gs8-20020a1709072d0800b007b273d1f664si14729030ejc.128.2022.12.05.16.20.10; Mon, 05 Dec 2022 16:20:29 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=oGxMdcr+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231602AbiLFAEW (ORCPT + 79 others); Mon, 5 Dec 2022 19:04:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37068 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229471AbiLFAEV (ORCPT ); Mon, 5 Dec 2022 19:04:21 -0500 Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0D941B9DF for ; Mon, 5 Dec 2022 16:04:19 -0800 (PST) Received: by mail-ua1-x933.google.com with SMTP id n21so2267651uaj.8 for ; Mon, 05 Dec 2022 16:04:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CN9j3kYVvyZ5N6wvjIbsfvlwhZyZism7lUmKxfBm3qo=; b=oGxMdcr+0mbzD6dGaWRq//H9fg0RRqPLZS5um42zp6vqIB3VgaYSzsPlmIZ0z83+Fv O0goqZ/n6Ydm454x0iQFUjqVCxeoFtpDVFTBE9du6vbdkt9YG3ZYp92U/vktU881pzhA TdULRQ7aMupkPxWWZEdtAR6mtIm7nO7d+DpeE0VozhOJiaCMYZFnrHBjhAFZA2TddYd3 4FNrEcJY9Zj1oXHpEMc/hpy1qAKRPd1BiJeMK+pmKSdo/Nvp3UsdQ3+DGAVLPrzsBoxm cMgfGpOQPSAK42PLPdHgQKnp9QJdnTE8tw8qQMd9MDguSBcsVsV5mTkWMbj06/QHcEZP LxTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CN9j3kYVvyZ5N6wvjIbsfvlwhZyZism7lUmKxfBm3qo=; b=kQchZ/5AukXccLN+1t0t6cjOm4RMEIMp5vO3LgRLU6xCEt4nJog0+4eXlLic2Zzgr5 zajt/U6WKsH1ew+9crAKkJNTBonEd9ap7z6OZfEg0hqKHiN2w7ef2pNaXUrttsaaVaC+ QcUsmMAF6AAtEvIOSeR/Vi5PxV9Yj7Nyw/MZZ/4ck/7T8I5V4vT/jaI3N+w88rpNS1QL X4uO6Sm2J+Z/Z+Iu5lcF7TdkMnJ45rDv9QvWNLlFrgjD4JfxhLRj3Fm40bvOcQJfaqog CWX0yQCumykluQzQRQ4Koe3r5FoMoYoEpMKo27CgIVNJYWYM/bcq0VXcVAWEoK7w7Mys nbNg== X-Gm-Message-State: ANoB5pnZAvDO+R6LclQ0jxurqJghPv1ITnA1O3ykhET0d4PpGzclCs9w slnfvGeYWUoBq8l1bZdG2bVYDczvaIg+1GcMP4KGZA== X-Received: by 2002:ab0:5517:0:b0:409:5403:c18 with SMTP id t23-20020ab05517000000b0040954030c18mr38785220uaa.51.1670285058552; Mon, 05 Dec 2022 16:04:18 -0800 (PST) MIME-Version: 1.0 References: <20221203011120.2361610-1-almasrymina@google.com> <87lenm1soh.fsf@yhuang6-desk2.ccr.corp.intel.com> In-Reply-To: <87lenm1soh.fsf@yhuang6-desk2.ccr.corp.intel.com> From: Mina Almasry Date: Mon, 5 Dec 2022 16:04:07 -0800 Message-ID: Subject: Re: [PATCH v1] [mm-unstable] mm: Fix memcg reclaim on memory tiered systems To: "Huang, Ying" Cc: Andrew Morton , Johannes Weiner , Michal Hocko , Roman Gushchin , Shakeel Butt , Muchun Song , Yang Shi , Yosry Ahmed , weixugc@google.com, fvdl@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 4, 2022 at 6:39 PM Huang, Ying wrote: > > Mina Almasry writes: > > > commit 3f1509c57b1b ("Revert "mm/vmscan: never demote for memcg > > reclaim"") enabled demotion in memcg reclaim, which is the right thing > > to do, however, I suspect it introduced a regression in the behavior of > > try_to_free_mem_cgroup_pages(). > > > > The callers of try_to_free_mem_cgroup_pages() expect it to attempt to > > reclaim - not demote - nr_pages from the cgroup. I.e. the memory usage > > of the cgroup should reduce by nr_pages. The callers expect > > try_to_free_mem_cgroup_pages() to also return the number of pages > > reclaimed, not demoted. > > > > However, what try_to_free_mem_cgroup_pages() actually does is it > > unconditionally counts demoted pages as reclaimed pages. So in practice > > when it is called it will often demote nr_pages and return the number of > > demoted pages to the caller. Demoted pages don't lower the memcg usage, > > and so I think try_to_free_mem_cgroup_pages() is not actually doing what > > the callers want it to do. > > > > I suspect various things work suboptimally on memory systems or don't > > work at all due to this: > > > > - memory.high enforcement likely doesn't work (it just demotes nr_pages > > instead of lowering the memcg usage by nr_pages). > > - try_charge_memcg() will keep retrying the charge while > > try_to_free_mem_cgroup_pages() is just demoting pages and not actually > > making any room for the charge. > > - memory.reclaim has a wonky interface. It advertises to the user it > > reclaims the provided amount but it will actually demote that amount. > > > > There may be more effects to this issue. > > > > To fix these issues I propose shrink_folio_list() to only count pages > > demoted from inside of sc->nodemask to outside of sc->nodemask as > > 'reclaimed'. > > > > For callers such as reclaim_high() or try_charge_memcg() that set > > sc->nodemask to NULL, try_to_free_mem_cgroup_pages() will try to > > actually reclaim nr_pages and return the number of pages reclaimed. No > > demoted pages would count towards the nr_pages requirement. > > > > For callers such as memory_reclaim() that set sc->nodemask, > > try_to_free_mem_cgroup_pages() will free nr_pages from that nodemask > > with either reclaim or demotion. > > Have you checked all callers? For example, IIUC, in > reclaim_clean_pages_from_list(), although sc.nodemask == NULL, the > demoted pages should be counted as reclaimed. I checked all call stacks leading to shrink_folio_list() now (at least I hope). Here is what I think they do and how I propose to handle them: - reclaim_clean_pages_from_list() & __node_reclaim() & balance_pgdat() These try to free memory from a specific node, and both demotion and reclaim from that node should be counted. I propose these calls set sc>nodemask = pgdat.node_id to signal to shrink_folio_list() that both demotion and reclaim from this node should be counted. - try_to_free_pages() Tries to free pages from a specific nodemask. It sets sc->nodemask to ac->nodemask. In this case pages demoted within the nodemask should not count. Pages demoted outside of the nodemask should count, which this patch already tries to do. - mem_cgroup_shrink_node() This is memcg soft limit reclaim. AFAIU only reclaim should be counted. It already sets sc->nodemask=NULL to indicate that it requires reclaim from all nodes and that only reclaimed memory should be counted, which this patch already tries to do. - try_to_free_mem_cgroup_pages() This is covered in the commit message. Many callers set nodemask=NULL indicating they want reclaim and demotion should not count. memory.reclaim sets nodemask depending on the 'nodes=' arg and wants demotion and reclaim from that nodemask. - reclaim_folio_list() Sets no_demotion = 1. No ambiguity here, only reclaims and counts reclaimed pages. If agreeable I can fix reclaim_clean_pages_from_list() & __node_reclaim() & balance_pgdat() call sites in v3. > How about count both > "demoted" and "reclaimed" in struct scan_control, and let callers to > determine how to use the number? > I don't think this is by itself enough. Pages demoted between 2 nodes that are both in sc->nodemask should not count, I think. So 'demoted' needs to be specifically pages demoted outside of the nodemask. We can do 2 things: 1. Only allow the kernel to demote outside the nodemask (which you don't prefer). 2. Allow the kernel to demote inside the nodemask but not count them. I will see if I can implement #2. > > Tested this change using memory.reclaim interface. With this change, > > > > echo "1m" > memory.reclaim > > > > Will cause freeing of 1m of memory from the cgroup regardless of the > > demotions happening inside. > > > > echo "1m nodes=0" > memory.reclaim > > Have you tested these tests in the original kernel? If so, whether does > the issue you suspected above occurs during testing? > Yes. I set up a test case where I allocate 500m in a cgroup, and then do: echo "50m" > memory.reclaim Without my fix, my kernel demotes 70mb and reclaims 4 mb. With my v1 fix, my kernel demotes all memory possible and reclaims 60mb. I will add this to the commit message in the next version. > Best Regards, > Huang, Ying > > > Will cause freeing of 1m of node 0 by demotion if a demotion target is > > available, and by reclaim if no demotion target is available. > > > > Signed-off-by: Mina Almasry > > > > --- > > > > This is developed on top of mm-unstable largely because I need the > > memory.reclaim nodes= arg to test it properly. > > --- > > mm/vmscan.c | 13 ++++++++++++- > > 1 file changed, 12 insertions(+), 1 deletion(-) > > > > diff --git a/mm/vmscan.c b/mm/vmscan.c > > index 2b42ac9ad755..8f6e993b870d 100644 > > --- a/mm/vmscan.c > > +++ b/mm/vmscan.c > > @@ -1653,6 +1653,7 @@ static unsigned int shrink_folio_list(struct list_head *folio_list, > > LIST_HEAD(free_folios); > > LIST_HEAD(demote_folios); > > unsigned int nr_reclaimed = 0; > > + unsigned int nr_demoted = 0; > > unsigned int pgactivate = 0; > > bool do_demote_pass; > > struct swap_iocb *plug = NULL; > > @@ -2085,7 +2086,17 @@ static unsigned int shrink_folio_list(struct list_head *folio_list, > > /* 'folio_list' is always empty here */ > > > > /* Migrate folios selected for demotion */ > > - nr_reclaimed += demote_folio_list(&demote_folios, pgdat); > > + nr_demoted = demote_folio_list(&demote_folios, pgdat); > > + > > + /* > > + * Only count demoted folios as reclaimed if we demoted them from > > + * inside of the nodemask to outside of the nodemask, hence reclaiming > > + * pages in the nodemask. > > + */ > > + if (sc->nodemask && node_isset(pgdat->node_id, *sc->nodemask) && > > + !node_isset(next_demotion_node(pgdat->node_id), *sc->nodemask)) > > + nr_reclaimed += nr_demoted; > > + > > /* Folios that could not be demoted are still in @demote_folios */ > > if (!list_empty(&demote_folios)) { > > /* Folios which weren't demoted go back on @folio_list */ > > -- > > 2.39.0.rc0.267.gcb52ba06e7-goog >