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,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 AD75AC33CA2 for ; Thu, 9 Jan 2020 21:05:40 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 7ABE420721 for ; Thu, 9 Jan 2020 21:05:40 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7ABE420721 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 1CAAC8E0006; Thu, 9 Jan 2020 16:05:40 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 17A378E0001; Thu, 9 Jan 2020 16:05:40 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 08FF28E0006; Thu, 9 Jan 2020 16:05:40 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0049.hostedemail.com [216.40.44.49]) by kanga.kvack.org (Postfix) with ESMTP id E7E688E0001 for ; Thu, 9 Jan 2020 16:05:39 -0500 (EST) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with SMTP id A9910181AC9CC for ; Thu, 9 Jan 2020 21:05:39 +0000 (UTC) X-FDA: 76359327198.23.page22_88ae0c92dbe28 X-HE-Tag: page22_88ae0c92dbe28 X-Filterd-Recvd-Size: 2629 Received: from jabberwock.ucw.cz (jabberwock.ucw.cz [46.255.230.98]) by imf31.hostedemail.com (Postfix) with ESMTP for ; Thu, 9 Jan 2020 21:05:38 +0000 (UTC) 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) X-Bogosity: Ham, tests=bogofilter, spamicity=0.006815, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: --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--