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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 0D992C433DF for ; Tue, 18 Aug 2020 09:26:22 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id B57CA20786 for ; Tue, 18 Aug 2020 09:26:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B57CA20786 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 140206B002D; Tue, 18 Aug 2020 05:26:21 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0C8A16B002F; Tue, 18 Aug 2020 05:26:21 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id ED2436B0030; Tue, 18 Aug 2020 05:26:20 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0240.hostedemail.com [216.40.44.240]) by kanga.kvack.org (Postfix) with ESMTP id D3E706B002D for ; Tue, 18 Aug 2020 05:26:20 -0400 (EDT) Received: from smtpin28.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 991D3180AD81D for ; Tue, 18 Aug 2020 09:26:20 +0000 (UTC) X-FDA: 77163158520.28.sleep76_5f114e22701e Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin28.hostedemail.com (Postfix) with ESMTP id 665D8F039 for ; Tue, 18 Aug 2020 09:26:20 +0000 (UTC) X-HE-Tag: sleep76_5f114e22701e X-Filterd-Recvd-Size: 2400 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf21.hostedemail.com (Postfix) with ESMTP for ; Tue, 18 Aug 2020 09:26:19 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 6DBFFAE59; Tue, 18 Aug 2020 09:26:44 +0000 (UTC) Date: Tue, 18 Aug 2020 11:26:17 +0200 From: Michal Hocko To: peterz@infradead.org Cc: Waiman Long , Andrew Morton , Johannes Weiner , Vladimir Davydov , Jonathan Corbet , Alexey Dobriyan , Ingo Molnar , Juri Lelli , Vincent Guittot , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org Subject: Re: [RFC PATCH 0/8] memcg: Enable fine-grained per process memory control Message-ID: <20200818092617.GN28270@dhcp22.suse.cz> References: <20200817140831.30260-1-longman@redhat.com> <20200818091453.GL2674@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200818091453.GL2674@hirez.programming.kicks-ass.net> X-Rspamd-Queue-Id: 665D8F039 X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam05 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: On Tue 18-08-20 11:14:53, Peter Zijlstra wrote: > On Mon, Aug 17, 2020 at 10:08:23AM -0400, Waiman Long wrote: > > Memory controller can be used to control and limit the amount of > > physical memory used by a task. When a limit is set in "memory.high" in > > a v2 non-root memory cgroup, the memory controller will try to reclaim > > memory if the limit has been exceeded. Normally, that will be enough > > to keep the physical memory consumption of tasks in the memory cgroup > > to be around or below the "memory.high" limit. > > > > Sometimes, memory reclaim may not be able to recover memory in a rate > > that can catch up to the physical memory allocation rate. In this case, > > the physical memory consumption will keep on increasing. > > Then slow down the allocator? That's what we do for dirty pages too, we > slow down the dirtier when we run against the limits. This is what we actually do. Have a look at mem_cgroup_handle_over_high. -- Michal Hocko SUSE Labs