From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 1AB92285041; Fri, 22 May 2026 03:59:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779422389; cv=none; b=rhSKubSTMdoQ7Ko7MKuPWHV4WVWe4j+cgsahrSDyRw0+ip5RsK6Kq/0GDOC6jSX93kHHXYH9YCpudYeYxbtxBq/5zn1spFlUoI5uwJOboYWVuhDK/YT4BtHqp8cmjdy4Tz3DuMEDs/sdt+WduxhlWqmkjlJQkF1HCq/XutfoqZw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779422389; c=relaxed/simple; bh=f1cRlrQaa8c+2t9khxERxAhv4PRbJsPxezKquJq/rNg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=uPkQSPo12d5HJ8pHuWdS4kwkjfahCTr1JzcbYaNAkLohEJmaIBajEgXbaWpkcE1DEOEHrzDcougNJCtNb/cXVB4zOXw2lUarGeSQ6fRDFabn8xvgncKKpxrYDOBJqgjY6z5HzPgoD7su1R3GMyQAmn6v5QrYwdR/kp67a21f3gc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=TY0ImQzy; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="TY0ImQzy" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6D00C1F000E9; Fri, 22 May 2026 03:59:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779422387; bh=H/gaClVuyqlkbt2yK/hC2NqGH4xbGZ4Tk12L6ljTkqY=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=TY0ImQzydhJitS5Ddrvd57wmJkpFKQRHHejclNNLrSp/Pt3ZjbuAZXZ6t/deQEjPo B6RG70234GDvgoN2I1JfdyuZjEp7N7PcfGq56V+OZOfrgX/Kj3BGrDRD6gMp7QdGaZ 3XwaJGMmhDnnGJ9avnNUQFntrpWJ2DEMUmgcarvpvvrVDL+W/u+6c95VquTHO8Ly9L YhjfG/p75Pd4tjFa4tixP2g+M6KlXSRuVMElS1m+U1YdvCaX4tSQDzEzY1TnKgRNIH 2N5F82yOOXvzqrpGDeJFwkB/Mn2fFSJD/5ZgU9X/duY2SuPkz1gG+tRoDpon4nQWBc dSLeX2oApTWMQ== Date: Fri, 22 May 2026 03:59:45 +0000 From: Jaegeuk Kim To: Matthew Wilcox Cc: Theodore Tso , Christoph Hellwig , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Akilesh Kailash , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-api@vger.kernel.org, Christian Brauner Subject: Re: [PATCH v2] f2fs: another way to set large folio by remembering inode number Message-ID: References: <20260409134538.3692605-1-jaegeuk@kernel.org> <20260521155748.GA79343@macsyma-wired.lan> Precedence: bulk X-Mailing-List: linux-api@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 05/21, Matthew Wilcox wrote: > On Thu, May 21, 2026 at 11:57:48AM -0400, Theodore Tso wrote: > > So let me get this straight. This is a magic xattr interface which is > > not even persisted in the file system, but instead sets a 32-bit > > bitmask in the struct inode which disappears once the inode gets > > flushed from the inode stack. And it uses a generic xattr name, > > "user.fadvise". > > > > There's no way in *hell* any other file system is likely to adopt such > > a broken interface, so why didn't you just use an ioctl to set this > > magic f2fs-specific flag? > > I mean, yes, this API is horrendous. But it's just another example of > f2fs thinking it's somehow special and not just enabling large folios > like other filesystems do. This hurts everyone, not just people who use > f2fs. >From the production viewpoint, I raised a concern on setting large folio by default, since that exhausts lots of high-order pages, which were needed for essential system services and critical apps.