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=-7.5 required=3.0 tests=MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 106ADC32771 for ; Thu, 9 Jan 2020 11:56:37 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id CEB1C20656 for ; Thu, 9 Jan 2020 11:56:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CEB1C20656 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 6C2318E0009; Thu, 9 Jan 2020 06:56:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 672D38E0001; Thu, 9 Jan 2020 06:56:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 588968E0009; Thu, 9 Jan 2020 06:56:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 43EEF8E0001 for ; Thu, 9 Jan 2020 06:56:36 -0500 (EST) Received: from smtpin10.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with SMTP id D8DAA180AD807 for ; Thu, 9 Jan 2020 11:56:35 +0000 (UTC) X-FDA: 76357943550.10.unit10_90dbf37f6e622 X-HE-Tag: unit10_90dbf37f6e622 X-Filterd-Recvd-Size: 3185 Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com [209.85.128.43]) by imf07.hostedemail.com (Postfix) with ESMTP for ; Thu, 9 Jan 2020 11:56:35 +0000 (UTC) Received: by mail-wm1-f43.google.com with SMTP id a5so2615380wmb.0 for ; Thu, 09 Jan 2020 03:56:35 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=AVu7sF9AqXnzaqXtf2hGbb5ay0l2XqpGGLIFiXxAyIY=; b=kBRy4fIcjJKzrYjOgyUi9rm+1/HwRmRvOiaipA4TL/BE0+kDTR2DybrU5zhprH5Wyn 4vKYF2CfRw9Hh6myb1o4QhXBVWM8FzF8KjiynE4irS4Q2Y4TEwyHkkDveEM6oFYkkdR/ WLrtEO1gpcj30udWSI4yleoQP1VkopuPVQyRoSV2uyOSfPhASCVprqGjrGhcE+YBZ659 QjNgrf2V/GhEiaQuQtP3dTXlq37ZwGxpWzdV+CNy+AlaqwmhkjuqL7FCOBmusSyZPiFO 19H1qgx2QHIpqks+x8hp3OS7os6Nnr0RUVzCbgA1jYJtbRW2UOwuK8u4v7kMI9bc6Dtr mg/A== X-Gm-Message-State: APjAAAXnWMWmvPARa0aV+t8Wdus29gySBNvdhIS9C8WAMahqJ9FO+Ufp 2zhykU3RFYm5kFIqEV3xO/k= X-Google-Smtp-Source: APXvYqw6vYZl9SKle2x6bZtbsHTReXL6R/DJcOKD9zX3l4RkFkT5xL6AG5K5K9yWMNfMDqwgRFGQeA== X-Received: by 2002:a1c:1dd7:: with SMTP id d206mr4326511wmd.5.1578570994379; Thu, 09 Jan 2020 03:56:34 -0800 (PST) Received: from localhost (prg-ext-pat.suse.com. [213.151.95.130]) by smtp.gmail.com with ESMTPSA id g21sm2573710wmh.17.2020.01.09.03.56.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jan 2020 03:56:33 -0800 (PST) Date: Thu, 9 Jan 2020 12:56:33 +0100 From: Michal Hocko To: Pavel Machek Cc: kernel list , Andrew Morton , linux-mm@kvack.org, akpm@linux-foundation.org Subject: Re: OOM killer not nearly agressive enough? Message-ID: <20200109115633.GR4951@dhcp22.suse.cz> References: <20200107204412.GA29562@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200107204412.GA29562@amd> User-Agent: Mutt/1.12.2 (2019-09-21) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000791, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue 07-01-20 21:44:12, Pavel Machek wrote: > Hi! > > I updated my userspace to x86-64, and now chromium likes to eat all > the memory and bring the system to standstill. > > Unfortunately, OOM killer does not react: > > 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. Does sysrq+f help? > Do we agree that OOM killer should have reacted way sooner? 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? > Is there something I can tweak to make it behave more reasonably? PSI based early OOM killing might help. See https://github.com/facebookincubator/oomd -- Michal Hocko SUSE Labs