Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1954148ybn; Thu, 26 Sep 2019 04:54:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqyXEBbWNxjDI6ttcd/vESn98Wmsw5c14Ul7HYjjsjnXaK/UTVGqSn17Uj1kKvgg/4Tb5+4q X-Received: by 2002:a50:ef02:: with SMTP id m2mr3121334eds.157.1569498897575; Thu, 26 Sep 2019 04:54:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569498897; cv=none; d=google.com; s=arc-20160816; b=dbO5somLDTUz6PwxwqTVmP9DQvwqJy4E5aJHWZuJofFgRrqk7wdsFI47issM5fmoCz tyo4bb7AoeSfRwVxg82KRUhvO8/2hHzyJt8Dw9sOHZb4rqXbC4rUM3Xr840YQdBoi27t E2iHGrr5TfnAq8RF8ZAJv7JDyrWRlgzLnnL7X+IhtQz2kMGVu08xoul7KW8Chmbtbikz 2+V2WPn/FPrpIz3o5DFCWVC1BcS1Az8fonSoNX2ICJJ6IX2w0RVIQ1DUooF9H7V8SAc1 /vGqUOoRfHsvixLns89xwyxoWnBAR+BrlhZCesUgg3yUdbR25p+RlEAN2bLVwkC0O2Uf yrrQ== 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=5txir/tmLzZv89uKDF4H0A+YVsC3vu0vRamvY+nB1L0=; b=AXHez4PMspfRk72fm6KGhRezbyN7utgVmFMwoeX1IlrWRzBLgBN28bLajvCttpIgGx sOtq+YC3DLg3EMQ/HRgq8xPKHHupmRNtTDhx7ukQl3Qe+fsg1gRQXVIjEF2cpUKReqbb swLBcJI+rsBqH4AbmgNtwx1V8kaHS9lEPK6/VwvmFqy7jR7nqZsxx6Lm2WXWBXdQQf4J khMPtOdGhyFm71ZE5mOBLc0ilG+VfnKHeMracFiVPUbA/04fRyNQeF2saakLromUduNT qb+YDmCKb9Q5ly45u/xQrqpFrmvQzJ/PZ8CLzxteQNmdrXD9Fw9yg2upJuud3gblh6er MXEg== 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 t16si1122580edd.269.2019.09.26.04.54.33; Thu, 26 Sep 2019 04:54:57 -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 S1726318AbfIZLt4 (ORCPT + 99 others); Thu, 26 Sep 2019 07:49:56 -0400 Received: from mx2.suse.de ([195.135.220.15]:50388 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725768AbfIZLt4 (ORCPT ); Thu, 26 Sep 2019 07:49:56 -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 A0D1EAEEC; Thu, 26 Sep 2019 11:49:54 +0000 (UTC) Date: Thu, 26 Sep 2019 13:49:53 +0200 From: Michal Hocko To: Johannes Weiner Cc: Andrew Morton , Roman Gushchin , Chris Down , Tejun Heo , Dennis Zhou , "linux-kernel@vger.kernel.org" , "cgroups@vger.kernel.org" , "linux-mm@kvack.org" , Kernel Team Subject: Re: [PATCH] mm: Proportional memory.{low,min} reclaim Message-ID: <20190926114953.GA1224@dhcp22.suse.cz> References: <20190124014455.GA6396@chrisdown.name> <20190128210031.GA31446@castle.DHCP.thefacebook.com> <20190128214213.GB15349@chrisdown.name> <20190128215230.GA32069@castle.DHCP.thefacebook.com> <20190715153527.86a3f6e65ecf5d501252dbf1@linux-foundation.org> <20190716172459.GB16575@cmpxchg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190716172459.GB16575@cmpxchg.org> 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 [Hmm, this one somehow slipped through. sorry about that] On Tue 16-07-19 13:24:59, Johannes Weiner wrote: > On Mon, Jul 15, 2019 at 03:35:27PM -0700, Andrew Morton wrote: > > On Mon, 28 Jan 2019 21:52:40 +0000 Roman Gushchin wrote: > > > > > > Hmm, this isn't really a common situation that I'd thought about, but it > > > > seems reasonable to make the boundaries when in low reclaim to be between > > > > min and low, rather than 0 and low. I'll add another patch with that. Thanks > > > > > > It's not a stopper, so I'm perfectly fine with a follow-up patch. > > > > Did this happen? > > > > I'm still trying to get this five month old patchset unstuck :(. The > > review status is: > > > > [1/3] mm, memcg: proportional memory.{low,min} reclaim > > Acked-by: Johannes > > Reviewed-by: Roman > > > > [2/3] mm, memcg: make memory.emin the baseline for utilisation determination > > Acked-by: Johannes > > > > [3/3] mm, memcg: make scan aggression always exclude protection > > Reviewed-by: Roman > > I forgot to send out the actual ack-tag on #, so I just did. I was > involved in the discussions that led to that patch, the code looks > good to me, and it's what we've been using internally for a while > without any hiccups. > > > I do have a note here that mhocko intended to take a closer look but I > > don't recall whether that happened. > > Michal acked #3 in 20190530065111.GC6703@dhcp22.suse.cz. Afaik not the > others, but #3 also doesn't make a whole lot of sense without #1... > > > a) say what the hell and merge them or > > b) sit on them for another cycle or > > c) drop them and ask Chris for a resend so we can start again. > > Michal, would you have time to take another look this week? Otherwise, > I think everyone who would review them has done so. I do not remember objecting to this particular patch. I also admit I do not remember much about it either. I am unlikely to get to review this in more depth these days. It seems more people have reviewed it already so just go ahead. -- Michal Hocko SUSE Labs