Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1608397pxb; Wed, 20 Oct 2021 08:23:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw4UvCqJajUPPTP8XNk70bC7vDWNlDmOyL2oAYq3+5y/6RKy3EA1JvZdwwBUgxXf7opzRDy X-Received: by 2002:a17:906:7fc9:: with SMTP id r9mr221967ejs.542.1634743395238; Wed, 20 Oct 2021 08:23:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634743395; cv=none; d=google.com; s=arc-20160816; b=ty3K+3yz/WFeoeQ5BMxu2m0OD7H7LSSv9NX5oGZ/7X6vjD2HMlsKUPgUHqStpmCL48 kWSQeLvU+ra90F8XjcrL5NHMJGWpMaFXbMgim7G1hascm7hVflPk3UwJPIHjP+pbXjOh ELF5mJFeJ5Hxd0vYtlXJXky5BQwS86k87NjG2zB/w6UbcHDj8W/1s4uO12BtMMTR4M8f Bk0H7rS+vukW/xmKE51ZYxEUCoCuTJ3RrwhnNOj+gsGP+HzABjKT+cyLw1n79rA/tpNE aJOFpmyrhedcYRsPUKSr62lNTag7tlo3WODNATGfoDWtCEbXL4Ad7PY7qV3oBY53MRT6 s4Lg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=k06namyf963AyxI9h+hXT9BGU45vrBd4uWCXlMrWqhs=; b=bjqgP7soDHBkaWE8g8DRnkzjKjodAjcOEHro6a85Fbho5X8LxugTV3NOIHyLtrNYJt M8tN6Vx2nlgaEPr1HZSBgk1O2i9pVrTn3M1t3+ySVP7a1KZbDObcj5fjYBgAlf/MuapN sB2dwV3NpeCowm/4vGzsZsxhQjF5sT/lQMFS6ait5kc6bSVJwGfAQGHPin2MADpiMzW8 Eci4y4fF8y4yxZ5oyqL1kxhjtswGga+OFNELVV/XDHNMufJBkAH0+pbmWQ7eEN9uHxLE kCWWoNp5myy1Quty8rSdGalt8ULtUicCRFvPWuoKzVSu/3juz5YesZIZ52E10TymR5kx EuBg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id mp13si4649794ejc.436.2021.10.20.08.22.46; Wed, 20 Oct 2021 08:23:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230401AbhJTPXL (ORCPT + 99 others); Wed, 20 Oct 2021 11:23:11 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:60121 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230234AbhJTPXJ (ORCPT ); Wed, 20 Oct 2021 11:23:09 -0400 Received: from fsav311.sakura.ne.jp (fsav311.sakura.ne.jp [153.120.85.142]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 19KFK2FR077596; Thu, 21 Oct 2021 00:20:03 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav311.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav311.sakura.ne.jp); Thu, 21 Oct 2021 00:20:02 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav311.sakura.ne.jp) Received: from [192.168.1.9] (M106072142033.v4.enabler.ne.jp [106.72.142.33]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id 19KFK2c3077592 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Oct 2021 00:20:02 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH memcg 2/3] memcg: remove charge forcinig for dying tasks To: Michal Hocko , Vasily Averin Cc: Johannes Weiner , Vladimir Davydov , Andrew Morton , Roman Gushchin , Uladzislau Rezki , Vlastimil Babka , Shakeel Butt , Mel Gorman , cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel@openvz.org References: <56180e53-b705-b1be-9b60-75e141c8560c@virtuozzo.com> From: Tetsuo Handa Message-ID: Date: Thu, 21 Oct 2021 00:20:02 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/10/20 23:57, Michal Hocko wrote: > One argument for removing it from here is the maintainability. Now you > have a memcg specific check which is not in sync with the oom. E.g. > out_of_memory does task_will_free_mem as the very first thing. You are > also automatically excluding oom killer for cases where that might make > a sense. What makes it possible to remove this check? This check was added because task_will_free_mem() in out_of_memory() does NOT work. See commit 7775face207922ea ("memcg: killed threads should not invoke memcg OOM killer").