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 0073FC433DF for ; Tue, 19 May 2020 17:19:46 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id A7531207D3 for ; Tue, 19 May 2020 17:19:45 +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="JfujCTW9" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A7531207D3 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 3C0AF8000A; Tue, 19 May 2020 13:19:45 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 371F1900002; Tue, 19 May 2020 13:19:45 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2B0158000A; Tue, 19 May 2020 13:19:45 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0218.hostedemail.com [216.40.44.218]) by kanga.kvack.org (Postfix) with ESMTP id 16E33900002 for ; Tue, 19 May 2020 13:19:45 -0400 (EDT) Received: from smtpin11.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id C7D9B248F for ; Tue, 19 May 2020 17:19:44 +0000 (UTC) X-FDA: 76834130688.11.laugh17_7227b35643b2f X-HE-Tag: laugh17_7227b35643b2f X-Filterd-Recvd-Size: 3230 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf15.hostedemail.com (Postfix) with ESMTP for ; Tue, 19 May 2020 17:19:44 +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 3773020709; Tue, 19 May 2020 17:19:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1589908783; bh=txoebJD0JXZyCTapEX8ZUQbQAQswISjk2s2w3ulXDWE=; h=From:To:Cc:Subject:Date:From; b=JfujCTW9jLrv4ctnEq9FVyBu1KsishZnGXXGMmu3c4O15PjKXp1ZrHMuZ8EItEGOY 8hkokd3gsyqYkUxmztzHEFsc7cV5DyU07OJKPmTUi5xcS07at64HQW1wKi0gDu2pFK g9aziApsS4Iibl3s6P6fHkYmjuLooRgw7eCgQGNE= 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 v4 0/4] memcg: Slow down swap allocation as the available space gets depleted Date: Tue, 19 May 2020 10:19:34 -0700 Message-Id: <20200519171938.3569605-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.000000, 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 v3: https://lore.kernel.org/linux-mm/20200515202027.3217470-1-kuba@kernel= .org/ 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 (4): mm: prepare for swap over-high accounting and penalty calculation mm: move penalty delay clamping out of calculate_high_delay() mm: move cgroup high memory limit setting into struct page_counter mm: automatically penalize tasks with high swap use Documentation/admin-guide/cgroup-v2.rst | 20 +++ include/linux/memcontrol.h | 4 +- include/linux/page_counter.h | 8 ++ mm/memcontrol.c | 173 +++++++++++++++++------- mm/page_counter.c | 5 + 5 files changed, 161 insertions(+), 49 deletions(-) --=20 2.25.4