Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2456390ybl; Thu, 9 Jan 2020 13:06:45 -0800 (PST) X-Google-Smtp-Source: APXvYqxYzqskOU9iIYndcZpaLy6XtNAF6yh/pN8303UvcqqbfXadOda/4shAUFLfQRun0rAWMWYT X-Received: by 2002:aca:b1d4:: with SMTP id a203mr4677754oif.150.1578604004895; Thu, 09 Jan 2020 13:06:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578604004; cv=none; d=google.com; s=arc-20160816; b=p8/P3PmvzcIkhGUs3ysCMRdLCG/wz2K7M71tG8JySNxcjzfuniM9tVKROzIoDRlmvJ IFo7qnv9gr0ScrU1qt5X0Lxwsk322EZ9euNLBy+4Tty5GBOMdDtB3jaGsN+25duD1zK5 teY4axOPUrTNMG6hNDikcB4b5OsyZwnH8sYT2Be7drYB75cVOg2dzVV7WhGyYDEQJmix cB1Pwebli48ltIo+6u8m24tzycpyOzbWHg2xDoa8uQLG10Q25Mz1KkwNJIwT13S2onuS wc8oAyX02VR87YcIHza5mNpufso8NcWZRGRqrpoMYpO3G6ZQa2s6JPrYI/rAMOBIVRzI +rQQ== 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=p2Ix/5BCu0jvBiX7ZuwLG13+v482+Vy0iWIPpU9Ai9w=; b=Jtcuhm1Lor5nZnnxOttchgEVNznWYwICUAEceBNUOHqqvX2AOBnE4trPypdSx5dIH8 8yQpGdeFQU1yuMXjmwrQego9XM1CG9OoRfknxyjcZUIB0Zsqv4RrMOuQClHv3cUk9J1T HEVDI4pPaSKUjBs/zG5O1rq8RG3xrVAIOjNt5Q/Rgh5zn1wL9oGJIGuyIbZXPqixlfSc p1+PB0ttqE8x7kpbJp6SpfvND2Ow8ehj/9ZfkmN+NaP49OnHWTq4YPnLmPICUyNFa7cC RbYDf3Lgw/vpUgn61x+X1pzkNBkB+fPfXe6G14eHern84QqMtA6OKH1MZlVLTLTx+LJd K6fQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x186si4038036oig.209.2020.01.09.13.06.33; Thu, 09 Jan 2020 13:06:44 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727876AbgAIVFi (ORCPT + 99 others); Thu, 9 Jan 2020 16:05:38 -0500 Received: from jabberwock.ucw.cz ([46.255.230.98]:34108 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725775AbgAIVFi (ORCPT ); Thu, 9 Jan 2020 16:05:38 -0500 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id E2A021C25CE; Thu, 9 Jan 2020 22:05:36 +0100 (CET) Date: Thu, 9 Jan 2020 22:05:36 +0100 From: Pavel Machek To: Michal Hocko Cc: kernel list , Andrew Morton , linux-mm@kvack.org, akpm@linux-foundation.org Subject: Re: OOM killer not nearly agressive enough? Message-ID: <20200109210535.GB1553@duo.ucw.cz> References: <20200107204412.GA29562@amd> <20200109115633.GR4951@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p4qYPpj5QlsIQJ0K" Content-Disposition: inline In-Reply-To: <20200109115633.GR4951@dhcp22.suse.cz> 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 --p4qYPpj5QlsIQJ0K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu 2020-01-09 12:56:33, Michal Hocko wrote: > On Tue 07-01-20 21:44:12, Pavel Machek wrote: > > Hi! > >=20 > > I updated my userspace to x86-64, and now chromium likes to eat all > > the memory and bring the system to standstill. > >=20 > > Unfortunately, OOM killer does not react: > >=20 > > I'm now running "ps aux", and it prints one line every 20 seconds or > > more. Do we agree that is "unusable" system? I attempted to do kill > > from other session. >=20 > Does sysrq+f help? >=20 > > Do we agree that OOM killer should have reacted way sooner? >=20 > This is impossible to answer without knowing what was going on at the > time. Was the system threshing over page cache/swap? In other words, is > the system completely out of memory or refaulting the working set all > the time because it doesn't fit into memory? What statistics are best to collect? Would the memory lines from top do the trick? I normally have gkrellm running, but I found its results hard to interpret. Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --p4qYPpj5QlsIQJ0K Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCXheVnwAKCRAw5/Bqldv6 8ltpAJ96WOJA8wlWQlNnrSUmaHkimRk6dwCdHRfTvxQxVf+vUV01MoDCPPpBrWw= =3Jem -----END PGP SIGNATURE----- --p4qYPpj5QlsIQJ0K--