From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from casper.infradead.org (casper.infradead.org [90.155.50.34])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F5833CF671
	for <linux-kernel@vger.kernel.org>; Wed,  3 Jun 2026 15:40:19 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1780501223; cv=none; b=EmqqTcC4noLtsR23DAooyHULcq8tVPo175RbPOKQ8vcPJo4AEDWfHBwN9UxWQz4uUtstEarWKPL4s5i9zz0y9xnoi/1dZgRcYE6etFOiQVW9XaMh5Ot0XyTZtYQT0nd5KCtiBI+jsSMMUmkg40OAz9HNJjH5k3dMzdsEF2PcxvA=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1780501223; c=relaxed/simple;
	bh=dmqk9Us23G2LHFj+bmBeLheIssvu//Y2p8UAKhF4YtA=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=PCeHx2+7RZehu89no1s/G1rojurY/DF2eHEnv3SYu1SUghHwGn0uu7z4RWIKdwYj85wKI5XYWgpaYFAKTYCam+c3dtTLKhqKSUe4fV9gZ1/ViQERxySCYCr/jARJeoJ+6Jd7pB1U+26m3A7S1w85U6AYiY6fwoOy+MNTypiM1Y8=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=pass smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=e2ZjQtRO; arc=none smtp.client-ip=90.155.50.34
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=infradead.org
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="e2ZjQtRO"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version:
	References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:
	Content-Transfer-Encoding:Content-ID:Content-Description;
	bh=FwyipsiWLdhyjXhTM3VU7vrDs7H1TSBGFHlVfKCBm+A=; b=e2ZjQtRO9TKskyAd8FXj1qnJaP
	/6auntyxaIMryecHQvKkbXTM9hvkURlS4I1/iGe3dDPikOVNcs9mViJeh7pzXp/f6g07ynVgi01Xr
	Iz4CQRqfLNRXx6bSeGZywfThMD9XCGhBNilJ47A3uaXF9GbqikbUSHkKEAvMqpliz2MvIfGe7Hx6h
	VPAStJDD480Cs4AUbGctmE25Sq9uaYaolhn17Z1Tz18SDv8StZCFivIVa4sV7RUxEwo7R1g1+zWy9
	itr2Re17m1iW3uWfOu6JAGj1ctTOE02ozhd6icRrXHeTZJYcJRLJNi/tfEFjf+7aw+S4Oc4sSyayg
	DU+3YhLQ==;
Received: from willy by casper.infradead.org with local (Exim 4.99.1 #2 (Red Hat Linux))
	id 1wUnh9-000000047mu-2mYd;
	Wed, 03 Jun 2026 15:39:51 +0000
Date: Wed, 3 Jun 2026 16:39:51 +0100
From: Matthew Wilcox <willy@infradead.org>
To: Jianyue Wu <wujianyue000@gmail.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>, Baoquan He <baoquan.he@linux.dev>,
	Tal Zussman <tz2294@columbia.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Li <chrisl@kernel.org>, Kairui Song <kasong@tencent.com>,
	Kemeng Shi <shikemeng@huaweicloud.com>,
	Nhat Pham <nphamcs@gmail.com>, Baoquan He <bhe@redhat.com>,
	Barry Song <baohua@kernel.org>,
	Youngjun Park <youngjun.park@lge.com>,
	Qi Zheng <qi.zheng@linux.dev>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Axel Rasmussen <axelrasmussen@google.com>,
	Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	David Hildenbrand <david@kernel.org>,
	Michal Hocko <mhocko@kernel.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] mm: move folio LRU code out of swap
Message-ID: <aiBKx7t7XRBWJLm_@casper.infradead.org>
References: <20260602-ch-swap-series-plus-folio-lru-cleanup-v3-0-5bbb567f8c99@gmail.com>
 <20260602-ch-swap-series-plus-folio-lru-cleanup-v3-2-5bbb567f8c99@gmail.com>
 <ah79c9IIuXt51ybs@casper.infradead.org>
 <aiAGrJsNm_uAf1qu@MiWiFi-R3L-srv>
 <aiAXwQQz0MeGrD1x@lucifer>
 <CAJxJ_jhTAS3gbo5AoLPGCUSchUPTsUVzkNVprg9pfzqXFpPEaA@mail.gmail.com>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJxJ_jhTAS3gbo5AoLPGCUSchUPTsUVzkNVprg9pfzqXFpPEaA@mail.gmail.com>

On Wed, Jun 03, 2026 at 08:29:44PM +0800, Jianyue Wu wrote:
> I'm posting v4 shortly. It keeps the rename to mm/folio_lru.c so this
> series stays a small cleanup on top of the swap_ops work. A broader
> mm/folio.c (together with Tal's folio_wait split and the util.c
> helpers Matthew mentioned) will be a separate follow-up
> once there is maintainer consensus on the file boundaries.

What's the hurry to post a v3?  It's not going in this merge window.
I don't mean that you should also pull in Tal's patch series, merely
that your series renames swap.c to folio.c (and we give serious thought
to whether we create a folio.h, or leave folio functions spread over
mm.h and swap.h)

Then Tal comes along afterwards and moves the folio locking functions
into your folio.c.