Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp360669ybt; Fri, 26 Jun 2020 01:00:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwKvEt9eBTxcZI+R+rzr63Pe7grRIoo6Z47loAIf3PcXuVh4o92lZcan0W3Ol7JRa4GOUVi X-Received: by 2002:a17:906:5006:: with SMTP id s6mr1451590ejj.294.1593158416081; Fri, 26 Jun 2020 01:00:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593158416; cv=none; d=google.com; s=arc-20160816; b=f54SKpnSCCo/ajDSej/eX+MRggm+6kYJx/oFJlDuIn9iYsetyfDl7jYKewh6XmsrLB 6J3mjb6nnx3i2fzPGzuvu/TrSW5rgAQUf+yMzuEwWXqcVJOgGcy2fiieLjGoQq6H1+Hf q0CQepzLidp7Rrvdmill+uKkyonze9DBY/NapewLJkZXPUYx3vQo45+ObPQRDoppAXas CCb5eQnVU7YeplbNBq17K/NRhq02D/Im3Je8R6JiPlW5/8Wgm9M1Sl18voUTGouGF/u8 zvKwg8ImzbsE7NRO8hNKRA7FAUXUPR6g2OLMGVJX+WwzMZ+y7UBH0qmBRoZ1ByoOJZSl 40mQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=58PCaFXBGVgS/HUhghxByfA4GcHWesPQr1uJfgcYC3Y=; b=APnvsYKiRSr8GFvnN50+kVk+ly8/T6DHjtqQ6bhn4xylLn4vqmsSZ6uwCE0OSO54X6 BAxGjJJYTWha12t4evlN74qtdtrXyohPsTPtJENOWtp2CPWZnyw8zdnRxF6FSLnXlbWC naFGzymcKbgHHIWa0csCioX8Kpp7ARl5w5aR0cx7NYZ+GeehQpLQ5Jq/ZzBqecuPRwiJ 1SIG7dAjNTn2j2e1459pl9vxIQklAPLYmzsk4OUEkGWJ+Uxsavs+XL1Zp0qEUvoR/1JW L6ILNXoU+b3MIGjzaVcrWre1599M6Sai0DFlhhg/mhQGjaOcx5Jq2EwutsgA1y5jOJ8R eF2g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id de11si16555188edb.306.2020.06.26.00.59.53; Fri, 26 Jun 2020 01:00:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729026AbgFZH72 (ORCPT + 99 others); Fri, 26 Jun 2020 03:59:28 -0400 Received: from mx2.suse.de ([195.135.220.15]:33634 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728949AbgFZH7W (ORCPT ); Fri, 26 Jun 2020 03:59:22 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 87026AE25; Fri, 26 Jun 2020 07:59:19 +0000 (UTC) Date: Fri, 26 Jun 2020 09:59:18 +0200 From: Daniel Wagner To: Dave Hansen Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, ben.widawsky@intel.com, alex.shi@linux.alibaba.com, tobin@kernel.org, cl@linux.com, akpm@linux-foundation.org, stable@kernel.org Subject: Re: [PATCH] mm/vmscan: restore zone_reclaim_mode ABI Message-ID: <20200626075918.dj6ioaon5iuhtg6k@beryllium.lan> References: <20200626003459.D8E015CA@viggo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200626003459.D8E015CA@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Dave On Thu, Jun 25, 2020 at 05:34:59PM -0700, Dave Hansen wrote: > > From: Dave Hansen > > I went to go add a new RECLAIM_* mode for the zone_reclaim_mode > sysctl. Like a good kernel developer, I also went to go update the > documentation. I noticed that the bits in the documentation didn't > match the bits in the #defines. Drop the this paragraph from the commit message. It doesn't add any necessart information. Please have a look at https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes > The VM evidently stopped caring about RECLAIM_ZONE at some point (or > never cared) and the #define itself was later removed as a cleanup. > Those things by themselves are fine. > > But, the _other_ bit locations also got changed. That's not OK because > the bit values are documented to mean one specific thing and users > surely rely on them meaning that one thing and not changing from > kernel to kernel. The end result is that if someone had a script > that did: > > sysctl vm.zone_reclaim_mode=1 > > That script went from doing nothing to writing out pages during > node reclaim after the commit in question. That's not great. > > Put the bits back the way they were and add a comment so something > like this is a bit harder to do again. Update the documentation to > make it clear that the first bit is ignored. > > Signed-off-by: Dave Hansen > Fixes: commit 648b5cf368e0 ("mm/vmscan: remove unused RECLAIM_OFF/RECLAIM_ZONE") > Acked-by: Ben Widawsky > Cc: Alex Shi > Cc: Daniel Wagner > Cc: "Tobin C. Harding" > Cc: Christoph Lameter > Cc: Andrew Morton > Cc: stable@kernel.org > --- > > b/Documentation/admin-guide/sysctl/vm.rst | 12 ++++++------ > b/mm/vmscan.c | 9 +++++++-- > 2 files changed, 13 insertions(+), 8 deletions(-) > > diff -puN mm/vmscan.c~mm-vmscan-restore-old-zone_reclaim_mode-abi mm/vmscan.c > --- a/mm/vmscan.c~mm-vmscan-restore-old-zone_reclaim_mode-abi 2020-06-25 17:32:11.559165912 -0700 > +++ b/mm/vmscan.c 2020-06-25 17:32:11.572165912 -0700 > @@ -4090,8 +4090,13 @@ module_init(kswapd_init) > */ > int node_reclaim_mode __read_mostly; > > -#define RECLAIM_WRITE (1<<0) /* Writeout pages during reclaim */ > -#define RECLAIM_UNMAP (1<<1) /* Unmap pages during reclaim */ > +/* > + * These bit locations are exposed in the vm.zone_reclaim_mode sysctl > + * ABI. New bits are OK, but existing bits can never change. > + */ > +#define RECLAIM_RSVD (1<<0) /* (currently ignored/unused) */ > +#define RECLAIM_WRITE (1<<1) /* Writeout pages during reclaim */ > +#define RECLAIM_UNMAP (1<<2) /* Unmap pages during reclaim */ > > /* > * Priority for NODE_RECLAIM. This determines the fraction of pages > diff -puN Documentation/admin-guide/sysctl/vm.rst~mm-vmscan-restore-old-zone_reclaim_mode-abi Documentation/admin-guide/sysctl/vm.rst > --- a/Documentation/admin-guide/sysctl/vm.rst~mm-vmscan-restore-old-zone_reclaim_mode-abi 2020-06-25 17:32:11.562165912 -0700 > +++ b/Documentation/admin-guide/sysctl/vm.rst 2020-06-25 17:32:11.572165912 -0700 > @@ -938,7 +938,7 @@ in the system. > This is value OR'ed together of > > = =================================== > -1 Zone reclaim on > +1 (bit currently ignored) > 2 Zone reclaim writes dirty pages out > 4 Zone reclaim swaps pages > = =================================== > @@ -948,11 +948,11 @@ that benefit from having their data cach > left disabled as the caching effect is likely to be more important than > data locality. > > -zone_reclaim may be enabled if it's known that the workload is partitioned > -such that each partition fits within a NUMA node and that accessing remote > -memory would cause a measurable performance reduction. The page allocator > -will then reclaim easily reusable pages (those page cache pages that are > -currently not used) before allocating off node pages. > +Consider enabling one or more zone_reclaim mode bits if it's known that the > +workload is partitioned such that each partition fits within a NUMA node > +and that accessing remote memory would cause a measurable performance > +reduction. The page allocator will take additional actions before > +allocating off node pages. I think the documentation update should not be part of this patch. This makes the back porting to stable more difficult. Thanks, Daniel