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=-1.0 required=3.0 tests=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 ABD0AC34033 for ; Tue, 18 Feb 2020 08:59:55 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6E21621D7D for ; Tue, 18 Feb 2020 08:59:55 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6E21621D7D 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 0BA066B0003; Tue, 18 Feb 2020 03:59:55 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 06D666B0006; Tue, 18 Feb 2020 03:59:55 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E9D626B0007; Tue, 18 Feb 2020 03:59:54 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0082.hostedemail.com [216.40.44.82]) by kanga.kvack.org (Postfix) with ESMTP id CEA006B0003 for ; Tue, 18 Feb 2020 03:59:54 -0500 (EST) Received: from smtpin03.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 68330181AEF1F for ; Tue, 18 Feb 2020 08:59:54 +0000 (UTC) X-FDA: 76502650308.03.wool37_39522a41b7f62 X-HE-Tag: wool37_39522a41b7f62 X-Filterd-Recvd-Size: 9313 Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by imf40.hostedemail.com (Postfix) with ESMTP for ; Tue, 18 Feb 2020 08:59:53 +0000 (UTC) Received: by mail-wr1-f65.google.com with SMTP id n10so20941532wrm.1 for ; Tue, 18 Feb 2020 00:59:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ncWC4Mq2l6vBbVjSqC884nuFwg00+CZRskS/qQU9zIw=; b=NXJrWXcFzv7dHFuhdSvSTA3n2EWzMP4vkJgruZRtCXrlRsw3FY/WN6RNs0aBtZC3LV 2S11FWOrUgfBvu+7T4NqEWKmXCzuS8EZPPfFYm8pZ9ZCNap6OLZmasV9AVSFmztkW5Ab Cj4GXBExpH5oFPRGQjMMYie9JVjbpPH5KbyBSplZm2ua7FvaLskqwuPYTozfXsHo73PY fT7wSICz69pGmj1F96xcVTIe9DQ5lYzMKrQDTmFvanYMx3TWPH1kjTzSOB/If8xmjWF1 EqU33t6NtdBsZjyV0SnIYIeZpjcAriim3vSBE54ZExinQmO4d8/LNJwQn7GOkhjNBOVP hDUw== X-Gm-Message-State: APjAAAXhBgBY228j9aIHfI6UNALOJNadPZEHlNZWyXJLx8uIsYe+Hff1 ImmXUXDTNi1ckxH2rL2uEXQ= X-Google-Smtp-Source: APXvYqy8BxA8rme+cZnU5vnOMuCp7mpJEJ0/Z1YSBszNu5Zgz3MfAu12pC5TVbN1RqIW2J1rnyCzFw== X-Received: by 2002:a05:6000:108c:: with SMTP id y12mr1597849wrw.366.1582016392862; Tue, 18 Feb 2020 00:59:52 -0800 (PST) Received: from localhost (prg-ext-pat.suse.com. [213.151.95.130]) by smtp.gmail.com with ESMTPSA id o7sm2657604wmh.11.2020.02.18.00.59.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 18 Feb 2020 00:59:51 -0800 (PST) Date: Tue, 18 Feb 2020 09:59:51 +0100 From: Michal Hocko To: Yafang Shao Cc: Roman Gushchin , Johannes Weiner , Vladimir Davydov , Andrew Morton , Chris Down , Linux MM , stable@vger.kernel.org Subject: Re: [PATCH resend] mm, memcg: reset memcg's memory.{min, low} for reclaiming itself Message-ID: <20200218085951.GE21113@dhcp22.suse.cz> References: <20200217092459.GG31531@dhcp22.suse.cz> <20200217132443.GM31531@dhcp22.suse.cz> <20200217140430.GO31531@dhcp22.suse.cz> <20200217143529.GQ31531@dhcp22.suse.cz> <20200217151417.GS31531@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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-02-20 10:09:06, Yafang Shao wrote: > On Mon, Feb 17, 2020 at 11:14 PM Michal Hocko wrote: > > > > On Mon 17-02-20 22:40:22, Yafang Shao wrote: > > > On Mon, Feb 17, 2020 at 10:35 PM Michal Hocko wrote: > > > > > > > > On Mon 17-02-20 22:28:38, Yafang Shao wrote: > > > > > On Mon, Feb 17, 2020 at 10:04 PM Michal Hocko wrote: > > > > > > > > > > > > On Mon 17-02-20 21:51:23, Yafang Shao wrote: > > > > > > > On Mon, Feb 17, 2020 at 9:24 PM Michal Hocko wrote: > > > > > > > > > > > > > > > > On Mon 17-02-20 21:08:12, Yafang Shao wrote: > > > > > > > > > On Mon, Feb 17, 2020 at 5:25 PM Michal Hocko wrote: > > > > > > > > > > > > > > > > > > > > On Sun 16-02-20 09:52:49, Yafang Shao wrote: > > > > > > > > > > > memory.{emin, elow} are set in mem_cgroup_protected(), and the values of > > > > > > > > > > > them won't be changed until next recalculation in this function. After > > > > > > > > > > > either or both of them are set, the next reclaimer to relcaim this memcg > > > > > > > > > > > may be a different reclaimer, e.g. this memcg is also the root memcg of > > > > > > > > > > > the new reclaimer, and then in mem_cgroup_protection() in get_scan_count() > > > > > > > > > > > the old values of them will be used to calculate scan count, that is not > > > > > > > > > > > proper. We should reset them to zero in this case. > > > > > > > > > > > > > > > > > > > > > > Here's an example of this issue. > > > > > > > > > > > > > > > > > > > > > > root_mem_cgroup > > > > > > > > > > > / > > > > > > > > > > > A memory.max=1024M memory.min=512M memory.current=800M > > > > > > > > > > > > > > > > > > > > > > Once kswapd is waked up, it will try to scan all MEMCGs, including > > > > > > > > > > > this A, and it will assign memory.emin of A with 512M. > > > > > > > > > > > After that, A may reach its hard limit(memory.max), and then it will > > > > > > > > > > > do memcg reclaim. Because A is the root of this reclaimer, so it will > > > > > > > > > > > not calculate its memory.emin. So the memory.emin is the old value > > > > > > > > > > > 512M, and then this old value will be used in > > > > > > > > > > > mem_cgroup_protection() in get_scan_count() to get the scan count. > > > > > > > > > > > That is not proper. > > > > > > > > > > > > > > > > > > > > Please document user visible effects of this patch. What does it mean > > > > > > > > > > that this is not proper behavior? > > > > > > > > > > > > > > > > > > In the memcg reclaim, if the target memcg is the root of the reclaimer, > > > > > > > > > the reclaimer should scan this memcg's all page cache pages in the LRU, > > > > > > > > > but now as the old memcg.{emin, elow} value are still there, it will get > > > > > > > > > a wrong protection value, > > > > > > > > > and the reclaimer can't reclaim the page cache pages protected by this > > > > > > > > > wrong protection. > > > > > > > > > > > > > > > > Could you be more specific please. Your example above says that emin is > > > > > > > > not going to be recalculated and stays at 512M even for a potential max > > > > > > > > limit reclaim. The min limit is still 512M so why is this value wrong? > > > > > > > > > > > > > > > > > > > > > > Because the relcaimers are changed or the root the relcaimer is changed. > > > > > > > > > > > > > > Kswapd begins to relcaim memcg-A. > > > > > > > kswapd > > > > > > > | > > > > > > > calculate the {emin, elow} for memcg-A > > > > > > > | > > > > > > > stores {emin, elow} in memory.{emin, elow} of memcg-A > > > > > > > | > > > > > > > This memory.{emin, elow} will protect the page cache pages in memcg-A > > > > > > > (See get_scan_count->mem_cgroup_protection) > > > > > > > | > > > > > > > exit > > > > > > > (And it won't relcaim memcg-A for a long time) > > > > > > > > > > > > > > > > > > > > > Then memcg relcaimer is woke up (reached the hard limit of memcg-A), > > > > > > > and the root of this new reclaimer is memcg-A. > > > > > > > > > > > > > > This memcg relcaimer begins to reclaim memcg-A. > > > > > > > memcg relcaimer > > > > > > > | > > > > > > > As the root of the relcaimer is memcg-A, it won't calculate emin, elow > > > > > > > for memcg-A. > > > > > > > (See if (memcg == root) in mem_cgroup_protected()) > > > > > > > | > > > > > > > The old memory.{emin, elow} will protect the page cache pages in memcg-A > > > > > > > (SO WE SHOULD CLEAR THE OLD VALUE) > > > > > > > > > > > > I am sorry but I still do not follow. Could you focus on _why_ the old > > > > > > value is no longer valid? > > > > > > > > > > Because for the new reclaimer the memory.{emin, elow} should be 0. > > > > > The old value may be not 0, but it was thought as 0 in the if > > > > > statement (if (memcg == root)). > > > > > > > > Why should it be 0 when the A.min is still 512MB? > > > > > > Because A's hard limit is reached and A is the root of memcg relcaimer. > > > > Confused. But your examples suggests that memory.max > memory.min so > > having an effective emin 0 or not doesn't make any difference. > > > > Why is it having an effective emin 0 if memory.max > memory.min ? > Note that effective emin is only set in function > mem_cgroup_protected(), so if we don't set it explicitly to 0 then it > can't be 0. > > Besides mem_cgroup_protected(), the effective emin also take effect in > the function mem_cgroup_protection(), but in this function it only use > the existed memory.emin rather than verifying memory.max > memory.min. > > So the real issue is in mem_cgroup_protection(), because the value it > is using may be an old value. I am sorry but I still do not follow. You keep focusing on talking about the code while I am really interested in the user visible semantic that you want to achieve. I am sorry to be dense here but believe me I am trying. Your example doesn't help much because the effective protection doesn't play any role in the limit reclaim there AFAICS. I would even argue that emin == min is the proper thing in your example. So I can only recommend you to rethink your usecase and try to describe it in a higher level way. Thanks! -- Michal Hocko SUSE Labs