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 717E3C02180 for ; Mon, 13 Jan 2025 14:07:49 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E09EA6B007B; Mon, 13 Jan 2025 09:07:48 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id D92616B0083; Mon, 13 Jan 2025 09:07:48 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C32D96B0085; Mon, 13 Jan 2025 09:07:48 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id A46DD6B007B for ; Mon, 13 Jan 2025 09:07:48 -0500 (EST) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 5C86F140403 for ; Mon, 13 Jan 2025 14:07:48 +0000 (UTC) X-FDA: 83002607016.21.DDC05DE Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.12]) by imf24.hostedemail.com (Postfix) with ESMTP id ACEA4180017 for ; Mon, 13 Jan 2025 14:07:45 +0000 (UTC) Authentication-Results: imf24.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=PWFY2oEy; spf=none (imf24.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 192.198.163.12) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1736777266; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=QaXzsFH83dyUkbTXXe/9qijh3hQF/Bd/Qt1Rgz9LN2A=; b=hDqFP4oEPNK39U9NjLO1fQMFGs2ktpIf78J4eHFDBD58F7Fh4qOCn2vwuJn43MvCpsY6S4 UbJQAINKEj4wubrMzaB1PsO+lIHY8m70nZb5zOUj0J5PBJwPX/PqpeQdswPZxhiWAaZYgI KpKGjrw45KRqbrhu6YO84wNC4CDrxKw= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1736777266; a=rsa-sha256; cv=none; b=yZVmdP19A27R1MiRQj40nSC7Nz5xxiHq2MJKgw1RR9RJz9S7OO/GN11ZiaFFoHFsLloC2y nmHbhZ43IUvuqFpX+whpB1a7zz6L1USppLGceSZy019kVIakfqKjoxeJ2Sf3YnTR/Q1Pi7 GimLmPJDijzuluTDSZeQSvFPyX97XKc= ARC-Authentication-Results: i=1; imf24.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=PWFY2oEy; spf=none (imf24.hostedemail.com: domain of kirill.shutemov@linux.intel.com has no SPF policy when checking 192.198.163.12) smtp.mailfrom=kirill.shutemov@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1736777266; x=1768313266; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Daub8vm06w8IcRjMHeGOmiLMe3eJdiQxwNfwcfeWF2w=; b=PWFY2oEya2gKp4UH/u95Wen8T2ElSIF52seiVM5EJmRMcB/GNchqw1IH o0VuuyX6XKYG2DZgKsxutnKRqQ36LnxEfugXH/TTIPk/ThpPRLFyQ0fhV h1X+Kv60tdC+x0aYG2rhNM34t9ybNd/xnuPcf2jBrik/I4FbmZUW5turk ji/6IbyL57LlJIWQNgLvRdPNyhPVOFT+8BQW60UmTDwq89oR22r17qDYz /EQ/QdY9DqQpAC+D1qUscEh8ULEq9isrX1rKkduKdy+z07op+65lzU+4g GYxMtNd0hQpiS+nLXojYvfzY09/RTxEW+6wMJSAyX89yOhU847zXMfxAA w==; X-CSE-ConnectionGUID: XMZ/6S7HT/qMPVk0XGt9Lg== X-CSE-MsgGUID: XMkV0OlIQougfnUFwafR5g== X-IronPort-AV: E=McAfee;i="6700,10204,11314"; a="40980057" X-IronPort-AV: E=Sophos;i="6.12,310,1728975600"; d="scan'208";a="40980057" Received: from fmviesa007.fm.intel.com ([10.60.135.147]) by fmvoesa106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jan 2025 06:07:37 -0800 X-CSE-ConnectionGUID: ubPh+2y6SDe1z80joJq8Kg== X-CSE-MsgGUID: asJbCXYfTLCwN1vcFS+m3A== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.12,310,1728975600"; d="scan'208";a="104448520" Received: from black.fi.intel.com ([10.237.72.28]) by fmviesa007.fm.intel.com with ESMTP; 13 Jan 2025 06:07:30 -0800 Received: by black.fi.intel.com (Postfix, from userid 1000) id DA7883B7; Mon, 13 Jan 2025 16:07:28 +0200 (EET) Date: Mon, 13 Jan 2025 16:07:28 +0200 From: "Kirill A. Shutemov" To: Matthew Wilcox Cc: Andrew Morton , Jens Axboe , "Jason A. Donenfeld" , Andi Shyti , Chengming Zhou , Christian Brauner , Christophe Leroy , Dan Carpenter , David Airlie , David Hildenbrand , Hao Ge , Jani Nikula , Johannes Weiner , Joonas Lahtinen , Josef Bacik , Masami Hiramatsu , Mathieu Desnoyers , Miklos Szeredi , Nhat Pham , Oscar Salvador , Ran Xiaokai , Rodrigo Vivi , Simona Vetter , Steven Rostedt , Tvrtko Ursulin , Vlastimil Babka , Yosry Ahmed , Yu Zhao , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org Subject: Re: [PATCH 0/8] mm: Remove PG_reclaim Message-ID: References: <20250113093453.1932083-1-kirill.shutemov@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: ACEA4180017 X-Rspam-User: X-Rspamd-Server: rspam07 X-Stat-Signature: 461w84zjq44eok14twj6qumj5dmq7qjy X-HE-Tag: 1736777265-234055 X-HE-Meta: U2FsdGVkX18pmKVq6CmUVt71bsre6NQuTT7JdbPdGMSZqOW158tKnPaaToZUx1eB0AQaUi+TUtSaqgytEBVgA63XccaghjdwelazIFNkTKnUYiKZN21IjMCG5GxXa3d3aSiRkx2wBAc7REn4snjl8RFD8FbxcZaQJznpn+Z1H/nSGXRip8YghENvs9SDkYKyeLr3K7MnPdn2m6ls+GywvN/VDvbuItULkCVV2ge9j2tjd5hYiPm53GoXXHf63hMwpnfN058H2uzAiMhaKybZGJ9nqU0sS8U61qZiLecdGa8KLbZOcqPNXvnIq7kjcL4Y3r/ZCDnzs3GlqDgP2x+r+nZsTMaTghNxkN94hqdehUsVSt88xBF17bl2T6kKgLgFPi98vPMxvzX0cSe+eO09nhyhYFtjl8ZGH5gzS5u5kW2NCfYKW/Wq815oMJnSgpdQz1FsX4UsIkOXt6+D/VczabOxu2NYHxpGEn6/Y1tvP1WIjym48GRNDHYfFFbQ7mIFUZXrCarid7xuyb/Q0tHnXFSWoZupRWcWImkEjD5WbzYsdkQvj5VNr5SWyegEY9At/w4LPlkYEoiGrgdkybDGau4kv7p37bkrl0MuJfXi9D3FdyZuXKVf2+9km7Vq5Svv9viST4jtzJ9IP5E6hhPUDdqH9RbyOyF+x5LdsyRPxIuNmPj9RhIoffGRbEZIRG8RIMXOc5e8XUVD1gVpdf5IHHyPEVdy2kdBRa3WQtoTGeOVh4Rov/jK9q2SxhyuE/wVfREU6gZORQrPnUg6p8ac7FyrWxIsGuQ3m1hkYviBXG54DT0rSTCe+RSIPOziYIxdk6W/AXaseaql8PdMmKGMAhmCPvyUUJXD7EsPfSigenUvJznPUGIa+3a/DGhNsxAg+D9bObFF+9/bZISgec0fm1gNFvLMzIEnHvcR4acii0eeoSzID2b+BBjeUuX0rK1jtoGeSbsszu1mgdoZZKo 4Fe5b6jL 60SyFTu46JywDqFyR9CJqScB5BvvmoozwQCDoU4QPKqLjb93Gka8XB3QQT7al9JaQxDUaFIniYYCOkCaluig06cml/RAoWE+upoXhoSOd4cAhizuu2HM1CzufoHMXm6pW1OYQ/b4ovhjn2z+cuYHja2rBgHEscKjG0zqfxpqn4PXy5oaBDqeerkWGP1TGED6RrGRIkRfvRdDBPxu0Wc45Wtnn+/mPvMn4ZCHJQYY3LFFoh3w= 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: List-Subscribe: List-Unsubscribe: On Mon, Jan 13, 2025 at 01:45:48PM +0000, Matthew Wilcox wrote: > On Mon, Jan 13, 2025 at 11:34:45AM +0200, Kirill A. Shutemov wrote: > > Use PG_dropbehind instead of PG_reclaim and remove PG_reclaim. > > I was hoping we'd end up with the name PG_reclaim instead of the name > PG_dropbehind. PG_reclaim is a better name for this functionality. I got burned by re-using the name with MAX_ORDER redefinition. I guess it is less risky as it is less used, but still... Anyway, it can be done with a patch on top of the patchset. We must get rid of current PG_reclaim first. -- Kiryl Shutsemau / Kirill A. Shutemov