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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 646EFC433FE for ; Thu, 27 Jan 2022 22:42:37 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id D1E246B0071; Thu, 27 Jan 2022 17:42:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id CCE276B0072; Thu, 27 Jan 2022 17:42:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id B94296B0073; Thu, 27 Jan 2022 17:42:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0228.hostedemail.com [216.40.44.228]) by kanga.kvack.org (Postfix) with ESMTP id AAB696B0071 for ; Thu, 27 Jan 2022 17:42:36 -0500 (EST) Received: from smtpin29.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 1A22B18209BD8 for ; Thu, 27 Jan 2022 22:42:36 +0000 (UTC) X-FDA: 79077542712.29.EA99E34 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf03.hostedemail.com (Postfix) with ESMTP id 6B09F2003C for ; Thu, 27 Jan 2022 22:42:35 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 99871B8238C; Thu, 27 Jan 2022 22:42:33 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 93342C340E4; Thu, 27 Jan 2022 22:42:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1643323352; bh=ybh+vNa1e2zVCBIHmgIav4rSBCIa4tEXBrjj/Zvd9DM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=lD8DNYdSP5VgdUVvLTzLs87NT6X2RUv/tVO0wVWZV57Mo8tiF+Cy9CVqnSr4Mr28N /4z/vln9zP3ZnibjoeX42f/bT+EANd4Y6/PvlZ8IiaLj4IayJe8a69r3sno42DD5jQ fiofeE7oSvVhmRsxcbaFoTER4oAWLDgl8zvqXutM= Date: Thu, 27 Jan 2022 14:42:29 -0800 From: Andrew Morton To: NeilBrown Cc: Jaegeuk Kim , Chao Yu , Jeff Layton , Ilya Dryomov , Miklos Szeredi , Trond Myklebust , Anna Schumaker , Ryusuke Konishi , "Darrick J. Wong" , Philipp Reisner , Lars Ellenberg , Paolo Valente , Jens Axboe , linux-mm@kvack.org, linux-nilfs@vger.kernel.org, linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-ext4@vger.kernel.org, ceph-devel@vger.kernel.org, drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org Subject: Re: [PATCH 0/9] Remove remaining parts of congestions tracking code. Message-Id: <20220127144229.a7109a508521db5e8ddda09c@linux-foundation.org> In-Reply-To: <164325106958.29787.4865219843242892726.stgit@noble.brown> References: <164325106958.29787.4865219843242892726.stgit@noble.brown> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam09 X-Rspamd-Queue-Id: 6B09F2003C X-Stat-Signature: c8gfgaz1xgrwwcx3irax9uuxh5g3gcrb X-Rspam-User: nil Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=lD8DNYdS; spf=pass (imf03.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-HE-Tag: 1643323355-451949 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, 27 Jan 2022 13:46:29 +1100 NeilBrown wrote: > Congestion hasn't been reliably tracked for quite some time. > Most MM uses of it for guiding writeback decisions were removed in 5.16. > Some other uses were removed in 17-rc1. > > This series removes the remaining places that test for congestion, and > the few places which still set it. > > The second patch touches a few filesystems. I didn't think there was > much value in splitting this out by filesystems, but if maintainers > would rather I did that, I will. > > The f2fs, cephfs, fuse, NFS, and block patches can go through the > respective trees proving the final patch doesn't land until after they > all do - so maybe it should be held for 5.18-rc2 if all the rest lands > by 5.18-rc1. Plan B: I'll just take everything. While collecting tested-bys and acked-bys from filesystem maintainers (please).