Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp7211853ybh; Thu, 8 Aug 2019 11:54:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqyRav27N88FN5910x5mDkPMMF3v6pag//01T1bEzY85lBXSRAOB9iHuIFi0iixDUhmauA9N X-Received: by 2002:a17:90a:346c:: with SMTP id o99mr5394998pjb.20.1565290458983; Thu, 08 Aug 2019 11:54:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565290458; cv=none; d=google.com; s=arc-20160816; b=mKQ2ie1rS0n/PKBIypbxquk0aBNQfjXsHxaT4qSDdBon5NKcGGHtSSRoUb9TrG5OSw 1kN9gN0Zdt+tK36vwrDlV4vSEOrvZvSq+H39vQJ89RhLcxA8sxpNqwcEIqPoIN48YDc9 b+OY8fYtweOu2CWBNO1kIZPQfae603aTTnX1tHMT/v7ZQxMMF1S+ybUmbSSio6UQ0+Zs 5YYdA9VlGAQu6WROYN4NdpI6ui+l4OhYPrd24Ekx/8CfFz+PTEtYEJlwv78zBs/MnIux FbPCxK0/y884aVfI1JtHARZcJ6LX829awDqjc/JHeDgQzLugDV/cWZApytGvzfC5yzIA aIkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=sghXZSHC0Xud5ECfy7tiTNcVVFX4jpjyj2brc/S5i/I=; b=VwPxH8ld7acaNtGh0RfYW60rcQ8gQTekzJAxNw1fmu41YG1DQiJyRhOXApp7rytKj1 otzoetHN9usNa1ozCsAcFoeeUNaaWKAs7OUnIKkBpP9iyrQMG9wSIQyJymY78+LTE4Qs ulXhoASgmCtFqFDmgaEzIn56GnRsrlThPR9hhW95QYHjrGdWAimXB8tzcumbz0i5ZqGf dSKEUIMpXrhO+cIe5U1h2zZ0NPLJH99ERLZ1E2oJgHQKsOQKACA16ak7KverQ04Tv/nK wxOtoDAdJJC9ZE/FroWiTqo1JtqvZYIwhE5McOY3cvRs8O2rSqDDjvG/O5CxL0VpN6gX uyAw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 70si48310796plc.253.2019.08.08.11.54.02; Thu, 08 Aug 2019 11:54:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390253AbfHHSvY (ORCPT + 99 others); Thu, 8 Aug 2019 14:51:24 -0400 Received: from mx2.suse.de ([195.135.220.15]:44802 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1733248AbfHHSvX (ORCPT ); Thu, 8 Aug 2019 14:51:23 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 3E4BBAFA7; Thu, 8 Aug 2019 18:51:22 +0000 (UTC) Date: Thu, 8 Aug 2019 20:51:19 +0200 From: Michal Hocko To: Edward Chron Cc: Andrew Morton , Roman Gushchin , Johannes Weiner , David Rientjes , Tetsuo Handa , Shakeel Butt , linux-mm@kvack.org, linux-kernel@vger.kernel.org, colona@arista.com Subject: Re: [PATCH] mm/oom: Add killed process selection information Message-ID: <20190808185119.GF18351@dhcp22.suse.cz> References: <20190808183247.28206-1-echron@arista.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190808183247.28206-1-echron@arista.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 08-08-19 11:32:47, Edward Chron wrote: > For an OOM event: print oomscore, memory pct, oom adjustment of the process > that OOM kills and the totalpages value in kB (KiB) used in the calculation > with the OOM killed process message. This is helpful to document why the > process was selected by OOM at the time of the OOM event. > > Sample message output: > Jul 21 20:07:48 yoursystem kernel: Out of memory: Killed process 2826 > (processname) total-vm:1056800kB, anon-rss:1052784kB, file-rss:4kB, > shmem-rss:0kB memory-usage:3.2% oom_score:1032 oom_score_adj:1000 > total-pages: 32791748kB A large part of this information is already printed in the oom eligible task list. Namely rss, oom_score_adj, there is also page tables consumption which might be a serious contributor as well. Why would you like to see oom_score, memory-usage and total-pages to be printed as well? How is that information useful? -- Michal Hocko SUSE Labs