Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp360783imb; Fri, 1 Mar 2019 02:40:41 -0800 (PST) X-Google-Smtp-Source: APXvYqwRir+WNaKaKPBHMNPrcN92/3KA0fpqW9t118i7EnRood/KgqZs4lvLegaltaia5M1qLZv2 X-Received: by 2002:a17:902:1347:: with SMTP id r7mr4793475ple.82.1551436841174; Fri, 01 Mar 2019 02:40:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551436841; cv=none; d=google.com; s=arc-20160816; b=QTb0y5oPNu23F5WQupM42zgBokgEtAe/+abcgglxL0O34ZEAb7eY2RWsTHdhtJnX3S ZUAYMKiZ+70oyN3Fv2O92dHI1+nz7snJZrm8P0iqjmkyqthI9Do6iEofRnR7vpxlVkDY iUtpa4MsE4AaghKWWVZZhRpAUFqeU9EsNsHW8YCBDZn9oW3mVA04W29ZXeO2UJiQ6us6 bQE9cNXAIJ5JkF3jO+MYnhNhx7K68OO0USv+OrjzuKU3NkD7MtQDm4FFaLP80O3A04bD FMkRckpJMYst7lvi1fyFWA9pRbz0fzLXQLT6m6tHEl11KKVQRE7TmC3l4C+TedkNGsaf A0bw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:subject:from; bh=ckrZQp0PZ2mpaKZo10KFPTYDS8LaJ0tANgFIQmuYBt8=; b=PpA8ZVHVU6hTUCo37ZH3lesp6b/z7yJ1Qv37g9eZlCVe83WxYhB2U8FQEMzVUaH0ih tLophOT8aGZaA2L4kEQuGCTV0rmPKwXBBL0geoZ3dqgovDKos9uPijcECBRkNqwf3AP1 TtEAhz4nD3iY0E0PvuVnFbEQxJ0yvqDnXVXWb+ViZYIM4SxBZqRNCMBT0a+6390gJcJ1 YrCtH5rpTlC/eM2+MY1LGoJYKpAE6SwUDYVtpsPkAWyEQkjRhvlf3/3aDGOQu1AFiYDB eF12G72Z4DzRwYb5Szlz+neDh0CQsznFsb7TT51gVjPz1BxRHgCHtCWb5Hsgx05HV450 UZZg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=virtuozzo.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o19si19416432pll.407.2019.03.01.02.40.25; Fri, 01 Mar 2019 02:40:41 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=virtuozzo.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729591AbfCAKiW (ORCPT + 99 others); Fri, 1 Mar 2019 05:38:22 -0500 Received: from relay.sw.ru ([185.231.240.75]:40994 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727492AbfCAKiV (ORCPT ); Fri, 1 Mar 2019 05:38:21 -0500 Received: from [172.16.25.12] by relay.sw.ru with esmtp (Exim 4.91) (envelope-from ) id 1gzfYO-000469-Ez; Fri, 01 Mar 2019 13:38:08 +0300 From: Andrey Ryabinin Subject: Re: [PATCH RFC] mm/vmscan: try to protect active working set of cgroup from reclaim. To: Johannes Weiner Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Michal Hocko , Vlastimil Babka , Rik van Riel , Mel Gorman , Roman Gushchin , Shakeel Butt References: <20190222175825.18657-1-aryabinin@virtuozzo.com> <20190222191552.GA15922@cmpxchg.org> Message-ID: <7c915942-6f52-e7a4-b879-e4c99dd65968@virtuozzo.com> Date: Fri, 1 Mar 2019 13:38:26 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/26/19 3:50 PM, Andrey Ryabinin wrote: > > > On 2/22/19 10:15 PM, Johannes Weiner wrote: >> On Fri, Feb 22, 2019 at 08:58:25PM +0300, Andrey Ryabinin wrote: >>> In a presence of more than 1 memory cgroup in the system our reclaim >>> logic is just suck. When we hit memory limit (global or a limit on >>> cgroup with subgroups) we reclaim some memory from all cgroups. >>> This is sucks because, the cgroup that allocates more often always wins. >>> E.g. job that allocates a lot of clean rarely used page cache will push >>> out of memory other jobs with active relatively small all in memory >>> working set. >>> >>> To prevent such situations we have memcg controls like low/max, etc which >>> are supposed to protect jobs or limit them so they to not hurt others. >>> But memory cgroups are very hard to configure right because it requires >>> precise knowledge of the workload which may vary during the execution. >>> E.g. setting memory limit means that job won't be able to use all memory >>> in the system for page cache even if the rest the system is idle. >>> Basically our current scheme requires to configure every single cgroup >>> in the system. >>> >>> I think we can do better. The idea proposed by this patch is to reclaim >>> only inactive pages and only from cgroups that have big >>> (!inactive_is_low()) inactive list. And go back to shrinking active lists >>> only if all inactive lists are low. >> >> Yes, you are absolutely right. >> >> We shouldn't go after active pages as long as there are plenty of >> inactive pages around. That's the global reclaim policy, and we >> currently fail to translate that well to cgrouped systems. >> >> Setting group protections or limits would work around this problem, >> but they're kind of a red herring. We shouldn't ever allow use-once >> streams to push out hot workingsets, that's a bug. >> >>> @@ -2489,6 +2491,10 @@ static void get_scan_count(struct lruvec *lruvec, struct mem_cgroup *memcg, >>> >>> scan >>= sc->priority; >>> >>> + if (!sc->may_shrink_active && inactive_list_is_low(lruvec, >>> + file, memcg, sc, false)) >>> + scan = 0; >>> + >>> /* >>> * If the cgroup's already been deleted, make sure to >>> * scrape out the remaining cache. >>> @@ -2733,6 +2739,7 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc) >>> struct reclaim_state *reclaim_state = current->reclaim_state; >>> unsigned long nr_reclaimed, nr_scanned; >>> bool reclaimable = false; >>> + bool retry; >>> >>> do { >>> struct mem_cgroup *root = sc->target_mem_cgroup; >>> @@ -2742,6 +2749,8 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc) >>> }; >>> struct mem_cgroup *memcg; >>> >>> + retry = false; >>> + >>> memset(&sc->nr, 0, sizeof(sc->nr)); >>> >>> nr_reclaimed = sc->nr_reclaimed; >>> @@ -2813,6 +2822,13 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc) >>> } >>> } while ((memcg = mem_cgroup_iter(root, memcg, &reclaim))); >>> >>> + if ((sc->nr_scanned - nr_scanned) == 0 && >>> + !sc->may_shrink_active) { >>> + sc->may_shrink_active = 1; >>> + retry = true; >>> + continue; >>> + } >> >> Using !scanned as the gate could be a problem. There might be a cgroup >> that has inactive pages on the local level, but when viewed from the >> system level the total inactive pages in the system might still be low >> compared to active ones. In that case we should go after active pages. >> >> Basically, during global reclaim, the answer for whether active pages >> should be scanned or not should be the same regardless of whether the >> memory is all global or whether it's spread out between cgroups. >> >> The reason this isn't the case is because we're checking the ratio at >> the lruvec level - which is the highest level (and identical to the >> node counters) when memory is global, but it's at the lowest level >> when memory is cgrouped. >> >> So IMO what we should do is: >> >> - At the beginning of global reclaim, use node_page_state() to compare >> the INACTIVE_FILE:ACTIVE_FILE ratio and then decide whether reclaim >> can go after active pages or not. Regardless of what the ratio is in >> individual lruvecs. >> >> - And likewise at the beginning of cgroup limit reclaim, walk the >> subtree starting at sc->target_mem_cgroup, sum up the INACTIVE_FILE >> and ACTIVE_FILE counters, and make inactive_is_low() decision on >> those sums. >> > > Sounds reasonable. > On the second thought it seems to be better to keep the decision on lru level. There are couple reasons for this: 1) Using bare node_page_state() (or sc->targe_mem_cgroup's total_[in]active counters) would be wrong. Because some cgroups might have protection set (memory.low) and we must take it into account. Also different cgroups have different available swap space/memory.swappiness and it must be taken into account as well to. So it has to be yet another full memcg-tree iteration. 2) Let's consider simple case. Two cgroups, one with big 'active' set of pages the other allocates one-time used pages. So the total inactive is low, thus checking inactive ratio on higher level will result in reclaiming pages. While with check on lru-level only inactive will be reclaimed. I've tried to come up with a scenario in which checking ratio on higher level would better but failed.