From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 11B4BC433DF for ; Fri, 15 May 2020 20:20:38 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id C0EF220728 for ; Fri, 15 May 2020 20:20:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="x6QV70Kf" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C0EF220728 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 539D58E0003; Fri, 15 May 2020 16:20:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 4EAD48E0001; Fri, 15 May 2020 16:20:37 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3FFC98E0003; Fri, 15 May 2020 16:20:37 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0008.hostedemail.com [216.40.44.8]) by kanga.kvack.org (Postfix) with ESMTP id 24A018E0001 for ; Fri, 15 May 2020 16:20:37 -0400 (EDT) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id C9C11181AC9CB for ; Fri, 15 May 2020 20:20:36 +0000 (UTC) X-FDA: 76820071272.22.net54_54c53c37cf24 X-HE-Tag: net54_54c53c37cf24 X-Filterd-Recvd-Size: 2978 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf50.hostedemail.com (Postfix) with ESMTP for ; Fri, 15 May 2020 20:20:36 +0000 (UTC) Received: from kicinski-fedora-PC1C0HJN.thefacebook.com (unknown [163.114.132.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1BE4020709; Fri, 15 May 2020 20:20:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1589574035; bh=P7ylBbnDPkXrGHK/uAPdYjg2MLbnpTgJJ00qvZ3qp38=; h=From:To:Cc:Subject:Date:From; b=x6QV70KfTY4U7aFjmudNZZrx1neH0SRoq5E45i9eURCIxREum4/9C9i1Aseq2AJe5 Rcnfsi8kUH40ncqWae+1ASsjMjW3Cw2/bSRwtXnULOD+2QM65mvT8BaPJbno8ZyKAI KFPK0FxiLJ71kuacaMmLLrtrwTfLjT3DG7hZwn24= From: Jakub Kicinski To: akpm@linux-foundation.org Cc: linux-mm@kvack.org, kernel-team@fb.com, tj@kernel.org, hannes@cmpxchg.org, chris@chrisdown.name, cgroups@vger.kernel.org, shakeelb@google.com, mhocko@kernel.org, Jakub Kicinski Subject: [PATCH mm v3 0/3] memcg: Slow down swap allocation as the available space gets depleted Date: Fri, 15 May 2020 13:20:24 -0700 Message-Id: <20200515202027.3217470-1-kuba@kernel.org> X-Mailer: git-send-email 2.25.4 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000004, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Tejun describes the problem as follows: When swap runs out, there's an abrupt change in system behavior - the anonymous memory suddenly becomes unmanageable which readily breaks any sort of memory isolation and can bring down the whole system. To avoid that, oomd [1] monitors free swap space and triggers kills when it drops below the specific threshold (e.g. 15%). While this works, it's far from ideal: - Depending on IO performance and total swap size, a given headroom might not be enough or too much. - oomd has to monitor swap depletion in addition to the usual pressure metrics and it currently doesn't consider memory.swap.max. Solve this by adapting parts of the approach that memory.high uses - slow down allocation as the resource gets depleted turning the depletion behavior from abrupt cliff one to gradual degradation observable through memory pressure metric. [1] https://github.com/facebookincubator/oomd v2: https://lore.kernel.org/linux-mm/20200511225516.2431921-1-kuba@kernel= .org/ v1: https://lore.kernel.org/linux-mm/20200417010617.927266-1-kuba@kernel.= org/ Jakub Kicinski (3): mm: prepare for swap over-high accounting and penalty calculation mm: move penalty delay clamping out of calculate_high_delay() mm: automatically penalize tasks with high swap use Documentation/admin-guide/cgroup-v2.rst | 20 +++ include/linux/memcontrol.h | 4 + mm/memcontrol.c | 159 ++++++++++++++++++------ 3 files changed, 143 insertions(+), 40 deletions(-) --=20 2.25.4