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.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 C01BCC433E0 for ; Thu, 18 Jun 2020 12:41:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9DBA62070A for ; Thu, 18 Jun 2020 12:41:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592484097; bh=iZBH7jkFydeVHaxRXDFbXNc28uxDlMTL2DjSf2j7Vas=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=2T+qJcqsHq513Cf4LVA3tmMOZJDrWdIvsUZgjxcD51zXNTBIqzmeCJVyQVi6O8c6V W7di8Zxzi/8XbpU+GZZp74N+gnKpKw/nsEU4USMRW+rUD1qDWljwPOG6hmBz8rM0NR lDV+a06Pz23IVh9GSPPQyC4rwqs8Wxpgl26nq21k= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727793AbgFRMlg (ORCPT ); Thu, 18 Jun 2020 08:41:36 -0400 Received: from mail-ej1-f65.google.com ([209.85.218.65]:40645 "EHLO mail-ej1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727091AbgFRMlg (ORCPT ); Thu, 18 Jun 2020 08:41:36 -0400 Received: by mail-ej1-f65.google.com with SMTP id q19so6243055eja.7; Thu, 18 Jun 2020 05:41:33 -0700 (PDT) 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=GwWWgp6poedvgja7RNEoGmK1y3wNcNo/q/dYBmBGoA8=; b=o8iKAGvPelZ799l0MgRR7gBeWope4OBEX/NDyfdtQx5l0XVPqxEXTLkzyAN8zAqTka pCTFcf4Mq3hXNkb73wjBquHHGOlZ0TV4DtXn7IsriCM5ZU2uu5gnd5ys4MEfFtVYASqe aovR3jFsdDdD5WpKqeR7mT+EoiB1BCO7Gm6c7Xu1Txjj6mXz4j5TMGt+yhHzYdOShA4W ZKjJBG6kCVog1crDs4rjS/+VuE7MVtYo9JyKTIikWISY5ySFs+N0d1ojPvHmzSjbQSKN RYHKamwenkP+F3qVryByBY1PJHDyCH0oFqkjWQbINQrlF/R+eeiPujCrBGsRDnglaOcs 6oYw== X-Gm-Message-State: AOAM533EKMj4LcuBj/8vMS6Z0z+u1pZd4xAn5TE1HUrnLeHZqgUxJiMH lyrhO7HzZyvFURM84sH880Y= X-Google-Smtp-Source: ABdhPJxMkauDVQefVPuJ2qpFGMV+90HykPa5BpTmZw4DM3T8iphGnLowIDqJy/XvxbHN8BtR+7Sktg== X-Received: by 2002:a17:907:20e5:: with SMTP id rh5mr3971654ejb.80.1592484092440; Thu, 18 Jun 2020 05:41:32 -0700 (PDT) Received: from localhost (ip-37-188-189-34.eurotel.cz. [37.188.189.34]) by smtp.gmail.com with ESMTPSA id dn15sm2375487ejc.26.2020.06.18.05.41.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 05:41:31 -0700 (PDT) Date: Thu, 18 Jun 2020 14:41:29 +0200 From: Michal Hocko To: Chris Down Cc: Yafang Shao , Naresh Kamboju , Anders Roxell , "Linux F2FS DEV, Mailing List" , linux-ext4 , linux-block , Andrew Morton , open list , Linux-Next Mailing List , linux-mm , Arnd Bergmann , Andreas Dilger , Jaegeuk Kim , Theodore Ts'o , Chao Yu , Hugh Dickins , Andrea Arcangeli , Matthew Wilcox , Chao Yu , lkft-triage@lists.linaro.org, Johannes Weiner , Roman Gushchin , Cgroups Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page Message-ID: <20200618124129.GC15447@dhcp22.suse.cz> References: <20200521163450.GV6462@dhcp22.suse.cz> <20200617135758.GA548179@chrisdown.name> <20200617141155.GQ9499@dhcp22.suse.cz> <20200617160624.GS9499@dhcp22.suse.cz> <20200617210935.GA578452@chrisdown.name> <20200618123743.GA694719@chrisdown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200618123743.GA694719@chrisdown.name> Sender: linux-block-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-block@vger.kernel.org On Thu 18-06-20 13:37:43, Chris Down wrote: > Yafang Shao writes: > > On Thu, Jun 18, 2020 at 5:09 AM Chris Down wrote: > > > > > > Naresh Kamboju writes: > > > >After this patch applied the reported issue got fixed. > > > > > > Great! Thank you Naresh and Michal for helping to get to the bottom of this :-) > > > > > > I'll send out a new version tomorrow with the fixes applied and both of you > > > credited in the changelog for the detection and fix. > > > > As we have already found that the usage around memory.{emin, elow} has > > many limitations, I think memory.{emin, elow} should be used for > > memcg-tree internally only, that means they can only be used to > > calculate the protection of a memcg in a specified memcg-tree but > > should not be exposed to other MM parts. > > I agree that the current semantics are mentally taxing and we should > generally avoid exposing the implementation details outside of memcg where > possible. Do you have a suggested rework? :-) I would really prefer to do that work on top of the fixes we (used to) have in mmotm (with the fixup). -- Michal Hocko SUSE Labs 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,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 C343DC433E0 for ; Thu, 18 Jun 2020 12:41:35 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 8EABB20663 for ; Thu, 18 Jun 2020 12:41:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8EABB20663 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 238A98D0001; Thu, 18 Jun 2020 08:41:35 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1E89C6B0096; Thu, 18 Jun 2020 08:41:35 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0D7608D0001; Thu, 18 Jun 2020 08:41:35 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0176.hostedemail.com [216.40.44.176]) by kanga.kvack.org (Postfix) with ESMTP id E6DCF6B0095 for ; Thu, 18 Jun 2020 08:41:34 -0400 (EDT) Received: from smtpin24.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 3B6F83584 for ; Thu, 18 Jun 2020 12:41:34 +0000 (UTC) X-FDA: 76942293708.24.floor91_100819226e10 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin24.hostedemail.com (Postfix) with ESMTP id 165771AA68 for ; Thu, 18 Jun 2020 12:41:34 +0000 (UTC) X-HE-Tag: floor91_100819226e10 X-Filterd-Recvd-Size: 4724 Received: from mail-ej1-f67.google.com (mail-ej1-f67.google.com [209.85.218.67]) by imf04.hostedemail.com (Postfix) with ESMTP for ; Thu, 18 Jun 2020 12:41:33 +0000 (UTC) Received: by mail-ej1-f67.google.com with SMTP id dr13so6256711ejc.3 for ; Thu, 18 Jun 2020 05:41:33 -0700 (PDT) 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=GwWWgp6poedvgja7RNEoGmK1y3wNcNo/q/dYBmBGoA8=; b=Qo2kMIK8Bd8Za7rPWAnIgz1EU3N6sBkG+SsvcUFMqho0oqB4jAPEorrwPZNkTZlF9g zV/5cI6WUVZ8GBPo05P4C/TW/6XHU7P5jziXNguNeWf6sFcEG7gf6qJUMhSJ9gsIzSUA Lct7jBguXpAIUt+0NzFYSv9K7k/Sm5kXkb99olCokyfM4xmMLbAyS1IV3LSiH1sP9Ea1 vYZUm4eLG+S2lqyac+RxLk7bpr0K0EPzSkBcermmRPUwijPEJVbHeEUYiBqdAfwjNZFx z62iAk2X7HLfy1wNJGyPxmaE+3xcWUQ8/pElTu947w4gj59IYzOCKtlldKbt5t/ycWMT +qHg== X-Gm-Message-State: AOAM5333u8aQAn8Yzg4jpZqdVYnmyT1qeS357l535rMISAP+TW564L7J bHB/7Aos5dm1goHSEhb0BuI= X-Google-Smtp-Source: ABdhPJxMkauDVQefVPuJ2qpFGMV+90HykPa5BpTmZw4DM3T8iphGnLowIDqJy/XvxbHN8BtR+7Sktg== X-Received: by 2002:a17:907:20e5:: with SMTP id rh5mr3971654ejb.80.1592484092440; Thu, 18 Jun 2020 05:41:32 -0700 (PDT) Received: from localhost (ip-37-188-189-34.eurotel.cz. [37.188.189.34]) by smtp.gmail.com with ESMTPSA id dn15sm2375487ejc.26.2020.06.18.05.41.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 05:41:31 -0700 (PDT) Date: Thu, 18 Jun 2020 14:41:29 +0200 From: Michal Hocko To: Chris Down Cc: Yafang Shao , Naresh Kamboju , Anders Roxell , "Linux F2FS DEV, Mailing List" , linux-ext4 , linux-block , Andrew Morton , open list , Linux-Next Mailing List , linux-mm , Arnd Bergmann , Andreas Dilger , Jaegeuk Kim , Theodore Ts'o , Chao Yu , Hugh Dickins , Andrea Arcangeli , Matthew Wilcox , Chao Yu , lkft-triage@lists.linaro.org, Johannes Weiner , Roman Gushchin , Cgroups Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page Message-ID: <20200618124129.GC15447@dhcp22.suse.cz> References: <20200521163450.GV6462@dhcp22.suse.cz> <20200617135758.GA548179@chrisdown.name> <20200617141155.GQ9499@dhcp22.suse.cz> <20200617160624.GS9499@dhcp22.suse.cz> <20200617210935.GA578452@chrisdown.name> <20200618123743.GA694719@chrisdown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200618123743.GA694719@chrisdown.name> X-Rspamd-Queue-Id: 165771AA68 X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam02 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000025, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu 18-06-20 13:37:43, Chris Down wrote: > Yafang Shao writes: > > On Thu, Jun 18, 2020 at 5:09 AM Chris Down wrote: > > > > > > Naresh Kamboju writes: > > > >After this patch applied the reported issue got fixed. > > > > > > Great! Thank you Naresh and Michal for helping to get to the bottom of this :-) > > > > > > I'll send out a new version tomorrow with the fixes applied and both of you > > > credited in the changelog for the detection and fix. > > > > As we have already found that the usage around memory.{emin, elow} has > > many limitations, I think memory.{emin, elow} should be used for > > memcg-tree internally only, that means they can only be used to > > calculate the protection of a memcg in a specified memcg-tree but > > should not be exposed to other MM parts. > > I agree that the current semantics are mentally taxing and we should > generally avoid exposing the implementation details outside of memcg where > possible. Do you have a suggested rework? :-) I would really prefer to do that work on top of the fixes we (used to) have in mmotm (with the fixup). -- Michal Hocko SUSE Labs 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=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 5E5CDC433DF for ; Thu, 18 Jun 2020 12:41:44 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 348C520C09 for ; Thu, 18 Jun 2020 12:41:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sourceforge.net header.i=@sourceforge.net header.b="eThLJios"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sf.net header.i=@sf.net header.b="AvJgsnMR" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 348C520C09 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com) by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1jltrT-0008Qw-RY; Thu, 18 Jun 2020 12:41:43 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-2.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jltrS-0008Qp-LZ for linux-f2fs-devel@lists.sourceforge.net; Thu, 18 Jun 2020 12:41:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=GwWWgp6poedvgja7RNEoGmK1y3wNcNo/q/dYBmBGoA8=; b=eThLJiosy47nUvmCfCClabwtIE nOwEeWHfdRq/aCH7rlY2Wmvs7ZRwFeG7RON9AsAOKGak4xGlTzxi1mBubfnMm67Zys+rdHfMYWYKp DMmSSfcTE1Glm6uRqMdXxJgzG1RdFTBWCJ8BUPK5iN0w+vwIbyOzqFK4ErRmKsqfzh+4=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To :From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=GwWWgp6poedvgja7RNEoGmK1y3wNcNo/q/dYBmBGoA8=; b=AvJgsnMRvhAxiMPgCePFvjbF0Q 1CKCt8vGGxnyuxHeGKMH063YbMZlK5WJSgj35k+ZFv6IhByGJMIKj4hNnul0wYZqmQFCn9ZaUuQJ8 IEMEZHA4pDobpzxwPp6foSgqxNROXebnIui5rcWWbQ1GtffrM3lJ81vl6dkKY4PtHR8w=; Received: from mail-ej1-f65.google.com ([209.85.218.65]) by sfi-mx-4.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.2) id 1jltrO-00AdKA-Qz for linux-f2fs-devel@lists.sourceforge.net; Thu, 18 Jun 2020 12:41:42 +0000 Received: by mail-ej1-f65.google.com with SMTP id y13so6264483eju.2 for ; Thu, 18 Jun 2020 05:41:38 -0700 (PDT) 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=GwWWgp6poedvgja7RNEoGmK1y3wNcNo/q/dYBmBGoA8=; b=o8Q5YFs3f6LisejGlCl01tijlA25MeOxTC8dVUVLRxoDya4UFMVu6MKRnpBgGxJm0Z 1ZGGzNr6w5Iixwd3T4f2R2yPOHClzxFTiU4G0CNy0kLpstQLz+URO67yU4y1KG6z38ez +JsYGcwmhOmkb/3FN/JfvVA+xlfbrFUclkqBThJRj+ov1thTkaivntxK0PaG+Nf0WKNo nBJx9CqMvCpH+nsisZnwukKuCijGkM8CGUDK1ecO1ktlu/tehqgXB1/NdT+/K0Ync429 jpx/mTfAsdrFF+LN5SBFMpsaC1p5mxUjgRtNflaclrvzJGPMCfoqlvEbrkWQg15/FbVV rmDQ== X-Gm-Message-State: AOAM531qpml/2r6dicAhlnwQoiS+/xvJj1GBK/7JVCTBgiO0DJQyJEPM yhS8DE9y8Xv9np5I3AT1vrE= X-Google-Smtp-Source: ABdhPJxMkauDVQefVPuJ2qpFGMV+90HykPa5BpTmZw4DM3T8iphGnLowIDqJy/XvxbHN8BtR+7Sktg== X-Received: by 2002:a17:907:20e5:: with SMTP id rh5mr3971654ejb.80.1592484092440; Thu, 18 Jun 2020 05:41:32 -0700 (PDT) Received: from localhost (ip-37-188-189-34.eurotel.cz. [37.188.189.34]) by smtp.gmail.com with ESMTPSA id dn15sm2375487ejc.26.2020.06.18.05.41.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 18 Jun 2020 05:41:31 -0700 (PDT) Date: Thu, 18 Jun 2020 14:41:29 +0200 From: Michal Hocko To: Chris Down Message-ID: <20200618124129.GC15447@dhcp22.suse.cz> References: <20200521163450.GV6462@dhcp22.suse.cz> <20200617135758.GA548179@chrisdown.name> <20200617141155.GQ9499@dhcp22.suse.cz> <20200617160624.GS9499@dhcp22.suse.cz> <20200617210935.GA578452@chrisdown.name> <20200618123743.GA694719@chrisdown.name> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20200618123743.GA694719@chrisdown.name> X-Headers-End: 1jltrO-00AdKA-Qz Subject: Re: [f2fs-dev] mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: lkft-triage@lists.linaro.org, linux-mm , Yafang Shao , Andreas Dilger , Cgroups , Andrea Arcangeli , Anders Roxell , Naresh Kamboju , Hugh Dickins , Matthew Wilcox , Linux-Next Mailing List , linux-ext4 , Arnd Bergmann , linux-block , Jaegeuk Kim , Theodore Ts'o , open list , "Linux F2FS DEV, Mailing List" , Johannes Weiner , Andrew Morton , Roman Gushchin Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On Thu 18-06-20 13:37:43, Chris Down wrote: > Yafang Shao writes: > > On Thu, Jun 18, 2020 at 5:09 AM Chris Down wrote: > > > > > > Naresh Kamboju writes: > > > >After this patch applied the reported issue got fixed. > > > > > > Great! Thank you Naresh and Michal for helping to get to the bottom of this :-) > > > > > > I'll send out a new version tomorrow with the fixes applied and both of you > > > credited in the changelog for the detection and fix. > > > > As we have already found that the usage around memory.{emin, elow} has > > many limitations, I think memory.{emin, elow} should be used for > > memcg-tree internally only, that means they can only be used to > > calculate the protection of a memcg in a specified memcg-tree but > > should not be exposed to other MM parts. > > I agree that the current semantics are mentally taxing and we should > generally avoid exposing the implementation details outside of memcg where > possible. Do you have a suggested rework? :-) I would really prefer to do that work on top of the fixes we (used to) have in mmotm (with the fixup). -- Michal Hocko SUSE Labs _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: mm: mkfs.ext4 invoked oom-killer on i386 - pagecache_get_page Date: Thu, 18 Jun 2020 14:41:29 +0200 Message-ID: <20200618124129.GC15447@dhcp22.suse.cz> References: <20200521163450.GV6462@dhcp22.suse.cz> <20200617135758.GA548179@chrisdown.name> <20200617141155.GQ9499@dhcp22.suse.cz> <20200617160624.GS9499@dhcp22.suse.cz> <20200617210935.GA578452@chrisdown.name> <20200618123743.GA694719@chrisdown.name> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20200618123743.GA694719@chrisdown.name> Sender: linux-block-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Chris Down Cc: Yafang Shao , Naresh Kamboju , Anders Roxell , "Linux F2FS DEV, Mailing List" , linux-ext4 , linux-block , Andrew Morton , open list , Linux-Next Mailing List , linux-mm , Arnd Bergmann , Andreas Dilger , Jaegeuk Kim , Theodore Ts'o , Chao Yu , Hugh Dickins , Andrea Arcangeli , Matthew Wilcox , Chao Yu , lkf On Thu 18-06-20 13:37:43, Chris Down wrote: > Yafang Shao writes: > > On Thu, Jun 18, 2020 at 5:09 AM Chris Down wrote: > > > > > > Naresh Kamboju writes: > > > >After this patch applied the reported issue got fixed. > > > > > > Great! Thank you Naresh and Michal for helping to get to the bottom of this :-) > > > > > > I'll send out a new version tomorrow with the fixes applied and both of you > > > credited in the changelog for the detection and fix. > > > > As we have already found that the usage around memory.{emin, elow} has > > many limitations, I think memory.{emin, elow} should be used for > > memcg-tree internally only, that means they can only be used to > > calculate the protection of a memcg in a specified memcg-tree but > > should not be exposed to other MM parts. > > I agree that the current semantics are mentally taxing and we should > generally avoid exposing the implementation details outside of memcg where > possible. Do you have a suggested rework? :-) I would really prefer to do that work on top of the fixes we (used to) have in mmotm (with the fixup). -- Michal Hocko SUSE Labs