Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2226764ybl; Thu, 29 Aug 2019 05:30:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqziViWNfd/yuG57G8i4+Z471+PhZuboPg40DPjdTQWk99deAYUeg7ddhaXMSnHkt7gKggRa X-Received: by 2002:a62:2c93:: with SMTP id s141mr11122433pfs.114.1567081826675; Thu, 29 Aug 2019 05:30:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567081826; cv=none; d=google.com; s=arc-20160816; b=DyaW3CMoK4kUdZr2GdVXq4Wv7EaB0B77QcnAUn5Oh8BP1Zu6Lxj2QMYpwvrCYMMSUn Xk/Mihydk9u/0jqNuHZqmnNf22WcHngtH6ijfpAPdU2/89/24dG/pXcAqKX6psQC4Ejh f1Zv96cg+Dp3KbgmIIr+1GafDuemnnS4wmkrttDMeCMy49TCExKCszq07T12pDTw9yvV SPtVMaVxt9/yqkMEMythT/SUjy5estz6UQvo9rZBYZUeFAmIsS95qtxl3L/Vg+JSrSKt 7pVabOVBy5gnQeU8MhzctcgcaYIe0YNPvSd2KwmLA+qOAY0bYIo/w7gJekI9Jxw1DNjF /aEA== 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=2iTlMn4Qr6IzwzXwFuey1zVc2ViIYWF7Hw0JXLz8A6Y=; b=fmGnv+9A5Sv9ho+ksFLhobjCUQC1QnyP2sHD+rtDDfpdXkbsZA8/aj4/Ssl2LJhkBP puvJJ2sOyswN2Zk3FyyzpHuL514cZAX+htnw53DPbe384svTwQRV80wWAmqSkgaiMEeg tukhss2Me7aTlx+oUSyRFTttohKmh0AgEzAczDPX470nJgSqJ2waeWz1oXKt0O19ROhn 6rEGHzhRbG40pPUfGd6KFVbtovxkYm8MB20dpn4/YLIyA3Je9LvK5AcroLqbynnOfR2y 1VTPIikkgDb4ryr0Ds6oSV1TA6Yc0HhqmUY0UOqTnp0epZz7lhtFgY/UBeWe7pYWqrZ0 je5w== 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 g4si1852913pgf.383.2019.08.29.05.30.10; Thu, 29 Aug 2019 05:30:26 -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 S1727014AbfH2M3M (ORCPT + 99 others); Thu, 29 Aug 2019 08:29:12 -0400 Received: from mx2.suse.de ([195.135.220.15]:35468 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725782AbfH2M3M (ORCPT ); Thu, 29 Aug 2019 08:29:12 -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 D8B80AC97; Thu, 29 Aug 2019 12:29:10 +0000 (UTC) Date: Thu, 29 Aug 2019 14:29:09 +0200 From: Michal Hocko To: James Courtier-Dutton Cc: Daniel Drake , "Artem S. Tashkinov" , LKML Mailing List , linux@endlessm.com, hadess@hadess.net, Johannes Weiner Subject: Re: Let's talk about the elephant in the room - the Linux kernel's inability to gracefully handle low memory pressure Message-ID: <20190829122909.GG28313@dhcp22.suse.cz> References: <20190820064620.5119-1-drake@endlessm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed 21-08-19 22:42:29, James Courtier-Dutton wrote: > On Tue, 20 Aug 2019 at 07:47, Daniel Drake wrote: > > > > Hi, > > > > And if there is a meaningful way to make the kernel behave better, that would > > obviously be of huge value too. > > > > Thanks > > Daniel > > Hi, > > Is there a way for an application to be told that there is a memory > pressure situation? PSI (CONFIG_PSI) measures global as well as per memcg pressure characteristics. [...] > I have also found, for the desktop, one of the biggest pressures on > the system is disk pressure. Accessing the disk causes the UI to be > less responsive. > For example, if I am in vim, and trying to type letters on the > keyboard, whether some other application is using the disk or not > should have no impact on my letter writing. Has anyone got any ideas > with regards to what we can do about that? This is what we have the page cache for. -- Michal Hocko SUSE Labs