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 24A34C433DF for ; Wed, 27 May 2020 19:58:52 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id B139420899 for ; Wed, 27 May 2020 19:58:51 +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="vsS3GJQY" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B139420899 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 36E698001A; Wed, 27 May 2020 15:58:51 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 2F79280010; Wed, 27 May 2020 15:58:51 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1E8E98001A; Wed, 27 May 2020 15:58:51 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0211.hostedemail.com [216.40.44.211]) by kanga.kvack.org (Postfix) with ESMTP id 0278780010 for ; Wed, 27 May 2020 15:58:50 -0400 (EDT) Received: from smtpin09.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id B2859824556B for ; Wed, 27 May 2020 19:58:50 +0000 (UTC) X-FDA: 76863562020.09.song77_4d2a62fe76f2a Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin09.hostedemail.com (Postfix) with ESMTP id 968FA180AD81D for ; Wed, 27 May 2020 19:58:50 +0000 (UTC) X-HE-Tag: song77_4d2a62fe76f2a X-Filterd-Recvd-Size: 3339 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf27.hostedemail.com (Postfix) with ESMTP for ; Wed, 27 May 2020 19:58:50 +0000 (UTC) Received: from kicinski-fedora-PC1C0HJN.thefacebook.com (unknown [163.114.132.1]) (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 6E5D620835; Wed, 27 May 2020 19:58:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1590609529; bh=cceq0nslNmPBHRGNvAoKjcHO4wn3WWeH8aZ2B6tbH7E=; h=From:To:Cc:Subject:Date:From; b=vsS3GJQY+3GrTaTAyo2NBKB3ea2HqlQR2dkWOfILWtaR4A+ZpBr3yneZCZEF9Hv2z sx4UHToiQuGHNRbjtIN2L6mteYz2c4iX5C3zYKGiE4pDoX4gJRdt13QfD9+GktJbsA OXmFO+iwSCBivypAZJPtHqhtl6PPsK8yVcKgvUVg= 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 v6 0/4] memcg: Slow down swap allocation as the available space gets depleted Date: Wed, 27 May 2020 12:58:42 -0700 Message-Id: <20200527195846.102707-1-kuba@kernel.org> X-Mailer: git-send-email 2.25.4 MIME-Version: 1.0 X-Rspamd-Queue-Id: 968FA180AD81D X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam04 Content-Transfer-Encoding: quoted-printable X-Bogosity: Ham, tests=bogofilter, spamicity=0.000021, 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 v5: https://lore.kernel.org/linux-mm/20200521002411.3963032-1-kuba@kernel= .org/ v4: https://lore.kernel.org/linux-mm/20200519171938.3569605-1-kuba@kernel= .org/ 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 | 177 ++++++++++++++++++------ 4 files changed, 160 insertions(+), 49 deletions(-) --=20 2.25.4