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=-5.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 8605AC433DB for ; Fri, 5 Feb 2021 10:21:52 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id F024F64E51 for ; Fri, 5 Feb 2021 10:21:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org F024F64E51 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine 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 54DCA6B006E; Fri, 5 Feb 2021 05:21:51 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 4FD7F6B0070; Fri, 5 Feb 2021 05:21:51 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4134A6B0073; Fri, 5 Feb 2021 05:21:51 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0019.hostedemail.com [216.40.44.19]) by kanga.kvack.org (Postfix) with ESMTP id 294586B006E for ; Fri, 5 Feb 2021 05:21:51 -0500 (EST) Received: from smtpin01.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id EB6BB180AD81F for ; Fri, 5 Feb 2021 10:21:50 +0000 (UTC) X-FDA: 77783823180.01.uncle50_2601d0c275e4 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin01.hostedemail.com (Postfix) with ESMTP id CF2161004720B for ; Fri, 5 Feb 2021 10:21:50 +0000 (UTC) X-HE-Tag: uncle50_2601d0c275e4 X-Filterd-Recvd-Size: 3592 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf50.hostedemail.com (Postfix) with ESMTP for ; Fri, 5 Feb 2021 10:21:50 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1612520509; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=441WHve7NP2TxAMx0OJ30INfKQWqrKfmb5j39ihe/DY=; b=vD+GXDhlMi+q+LG9eTNBL8QlKKkp0Yk2YsIRnv1U0jtK12zgNa84A5lVmwU25sEhOXR1g3 r/tOBtkZeacMgrU3FSrlbpsoUpc6zQv2UU0Pk7EeQE2dfk4jtBkU3TZXUhKrL67tRGs+5K iR6YLPQo02cieBvDO2ytc1YLsSVnVWI= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 181A3ACF4; Fri, 5 Feb 2021 10:21:49 +0000 (UTC) Date: Fri, 5 Feb 2021 11:21:47 +0100 From: Michal Hocko To: Muchun Song Cc: Johannes Weiner , Vladimir Davydov , Andrew Morton , Cgroups , Linux Memory Management List , LKML Subject: Re: [External] Re: [PATCH] mm: memcontrol: fix missing wakeup oom task Message-ID: References: <20210205062310.74268-1-songmuchun@bytedance.com> 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 Fri 05-02-21 17:55:10, Muchun Song wrote: > On Fri, Feb 5, 2021 at 4:24 PM Michal Hocko wrote: > > > > On Fri 05-02-21 14:23:10, Muchun Song wrote: > > > We call memcg_oom_recover() in the uncharge_batch() to wakeup OOM task > > > when page uncharged, but for the slab pages, we do not do this when page > > > uncharged. > > > > How does the patch deal with this? > > When we uncharge a slab page via __memcg_kmem_uncharge, > actually, this path forgets to do this for us compared to > uncharge_batch(). Right? Yes this was more more or less clear (still would have been nicer to be explicit). But you still haven't replied to my question I believe. I assume you rely on refill_stock doing draining but how does this address the problem? Is it sufficient to do wakeups in the batched way? > > > When we drain per cpu stock, we also should do this. > > > > Can we have anything the per-cpu stock while entering the OOM path. IIRC > > we do drain all cpus before entering oom path. > > You are right. I did not notice this. Thank you. > > > > > > The memcg_oom_recover() is small, so make it inline. > > > > Does this lead to any code generation improvements? I would expect > > compiler to be clever enough to inline static functions if that pays > > off. If yes make this a patch on its own. > > I have disassembled the code, I see memcg_oom_recover is not > inline. Maybe because memcg_oom_recover has a lot of callers. > Just guess. > > (gdb) disassemble uncharge_batch > [...] > 0xffffffff81341c73 <+227>: callq 0xffffffff8133c420 > 0xffffffff81341c78 <+232>: jmpq 0xffffffff81341bc0 > 0xffffffff81341c7d <+237>: callq 0xffffffff8133e2c0 So does it really help to do the inlining? -- Michal Hocko SUSE Labs