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=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 9B163C3A5A9 for ; Mon, 4 May 2020 15:44:20 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 6596D2063A for ; Mon, 4 May 2020 15:44:20 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6596D2063A Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=i-love.sakura.ne.jp Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id CC5628E0052; Mon, 4 May 2020 11:44:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C758A8E0024; Mon, 4 May 2020 11:44:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B648B8E0052; Mon, 4 May 2020 11:44:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0029.hostedemail.com [216.40.44.29]) by kanga.kvack.org (Postfix) with ESMTP id 9B7738E0024 for ; Mon, 4 May 2020 11:44:19 -0400 (EDT) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 5463B181AEF30 for ; Mon, 4 May 2020 15:44:19 +0000 (UTC) X-FDA: 76779458238.25.test90_8839c7aafa44 X-HE-Tag: test90_8839c7aafa44 X-Filterd-Recvd-Size: 3242 Received: from www262.sakura.ne.jp (www262.sakura.ne.jp [202.181.97.72]) by imf14.hostedemail.com (Postfix) with ESMTP for ; Mon, 4 May 2020 15:44:18 +0000 (UTC) Received: from fsav107.sakura.ne.jp (fsav107.sakura.ne.jp [27.133.134.234]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 044Fi1hv055060; Tue, 5 May 2020 00:44:01 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav107.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav107.sakura.ne.jp); Tue, 05 May 2020 00:44:01 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav107.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 044Fi0RI055015 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 May 2020 00:44:01 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH] memcg: oom: ignore oom warnings from memory.max To: Shakeel Butt Cc: Michal Hocko , Johannes Weiner , Roman Gushchin , Greg Thelen , Andrew Morton , Linux MM , Cgroups , LKML References: <20200430182712.237526-1-shakeelb@google.com> <20200504065600.GA22838@dhcp22.suse.cz> <939b6744-6556-2733-b83e-bf14e848dabd@I-love.SAKURA.ne.jp> From: Tetsuo Handa Message-ID: <3c24ef6a-f1f4-38e6-2d0f-1eac18dc15bb@i-love.sakura.ne.jp> Date: Tue, 5 May 2020 00:44:00 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 2020/05/04 23:57, Shakeel Butt wrote: > On Mon, May 4, 2020 at 7:20 AM Tetsuo Handa > wrote: >> >> On 2020/05/04 22:54, Shakeel Butt wrote: >>> It may not be a problem for an individual or small scale deployment >>> but when "sweep before tear down" is the part of the workflow for >>> thousands of machines cycling through hundreds of thousands of cgroups >>> then we can potentially flood the logs with not useful dumps and may >>> hide (or overflow) any useful information in the logs. >> >> I'm proposing a patch which allows configuring which OOM-related messages >> should be sent to consoles at >> https://lkml.kernel.org/r/20200424024239.63607-1-penguin-kernel@I-love.SAKURA.ne.jp . >> Will that approach help you? > >>>From what I understand, that patch is specifically for controlling > messages to consoles. The messages will still be in logs, right? > Right. If you want to control which OOM-related messages should be sent to syslog, we could use similar approach.