From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B2E5E2C0296 for ; Fri, 27 Feb 2026 02:02:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772157763; cv=none; b=MInicqqs9zYQsoWozuk0GsjcIQMMxWA9WZ3gS91eBe/doON10PiUtzuf5ePga5GMTqFmYWFMizeMNYJ6Iq0fyhvIqFnPCQZFMwUexHgbGm8H+XRa+FX/0cIUdhpeIE66SQYp6ae6rYG4r27Xktq/3cP6hWQr/qnUjWzGyyF7kn0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772157763; c=relaxed/simple; bh=/7c5bPHymBEdp2+pR/tjEKyv44kaAGF5s2JmpIBbPA4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Mw4/bqTH+gsKyZ7lpE7tMMMI/mu9TP7kupfWZ+40x1FduAE6TY36PxU0U0slCHOghM4yLFARM8KEgGF7fE6Lj12RkgD5Mo3PD7GJq3VrTtsXWPxecpt47tbxc+YUYSaD4ENct99oT+3iuyzF/7EkJ8+uJRKonF8Ex8yXKl2OZ0U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LbEAZ5ek; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="LbEAZ5ek" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DF4B1C116C6; Fri, 27 Feb 2026 02:02:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772157763; bh=/7c5bPHymBEdp2+pR/tjEKyv44kaAGF5s2JmpIBbPA4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LbEAZ5ekdUJk46mS2t0+AiG5EkCLzOZzKL4s8E+bNZBbVcWC1MLPzMW3ifZA2Gb+H RVQgXkkFomQR2fXZyUwTFq2eBObPE6zkMSpe7M7rVzzuFO5urP9Ai3TNZPdbrZO4Do V7wMDvcE/B8s88ACqrcMNswc2Gc/2e6MJQ1ERcj+dQMAvaRgWHkYjgx4bv17YWFihl 9A3nYq2x6EFQiYetxK+l2v6k5ZjneosTDj6g7FOmLHEMXmhhG6iSs6AB7eAo+oVpAc bapUi3urmtoJbtlA2W+kQOZkyJPee8GLBeOP51/fgwx3uAW2JbSzwVvRqyUg3fJLsw WVi/6uF+3VSMA== Date: Fri, 27 Feb 2026 02:02:41 +0000 From: Jaegeuk Kim To: Barry Song <21cnbao@gmail.com> Cc: Matthew Wilcox , Christoph Hellwig , Nanzhe Zhao , lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org, yi.zhang@huaweicloud.com, Chao Yu , wqu@suse.com Subject: Re: [LSF/MM/BPF TOPIC] Large folio support: iomap framework changes versus filesystem-specific implementations Message-ID: References: <75f43184.d57.19c7b2269dd.Coremail.nzzhao@126.com> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On 02/26, Barry Song wrote: > On Tue, Feb 24, 2026 at 5:36 AM Jaegeuk Kim wrote: > > > > On 02/20, Matthew Wilcox wrote: > > > On Fri, Feb 20, 2026 at 07:48:39AM -0800, Christoph Hellwig wrote: > > > > Maybe you catch on the wrong foot, but this pisses me off. I've been > > > > telling you guys to please actually fricking try converting f2fs to > > > > iomap, and it's been constantly ignored. > > > > > > Christoph isn't alone here. There's a consistent pattern of f2fs going > > > off and doing weird shit without talking to anyone else. A good start > > > would be f2fs maintainers actually coming to LSFMM, but a lot more design > > > decisions need to be cc'd to linux-fsdevel. > > > > What's the benefit of supporting the large folio on the write path? And, > > which other designs are you talking about? > > > > I'm also getting the consistent pattern: 1) posting patches in f2fs for > > production, 2) requested to post patches modifying the generic layer, 3) > > posting the converted patches after heavy tests, 4) sitting there for > > months without progress. > > It can sometimes be a bit tricky for the common layer and > filesystem-specific layers to coordinate smoothly. At times, > it can be somewhat frustrating. > > Privately, I know how tough it was for Nanzhe to decide whether > to make changes in the iomap layer or in filesystem-specific code. > Nevertheless, he has the dedication and care to implement F2FS > large folio support in the best possible way, as he has discussed > with me many times in private. > > I strongly suggest that LSF/MM/BPF invite Kim (and Chao, if possible) > along with the iomap team to discuss this together—at least > remotely if not everyone can attend in person. We don't have a plan to attend this year summit. But I'm open to have an offline call to discuss about what we can do in f2fs, if you guys are interested in. Let me know. > > > > > E.g., > > https://lore.kernel.org/lkml/20251202013212.964298-1-jaegeuk@kernel.org/ > > Thanks > Barry