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 1044B248F77 for ; Mon, 1 Dec 2025 21:24: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=1764624284; cv=none; b=kjVxjLaWgfm8SwkigWOKJaFjn3xunuDUrfNyexdfbRnYugbzRAVd16sh2MIvWloH6xnxWpDJXlxMQbAE+1WZIvu1DWiShvj7/bMCkYIrdbUHLwH/CPFyakce2baspo4Adjs2AlTBvIQOAN2MGMiMZUGa+Nq8zwzFcUvqmXZXYKk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764624284; c=relaxed/simple; bh=Diz0+bACmjM2TLHSfLwYpuxzqSwiJwi5SM5gyk06rTM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Ani7/sDj8gve/g/WdLKJ4N8VJ7jZWMIvgeDLVBkGkKR/NZYU4RGMjhFGXf62JaNZ3YloI54KdinlYkMwdBa6yh7r0covV5pVaDruSEtRk1mfKBpRZbCRPLvfctdJZETFHKrKO5qL/vOauPvSf9Z49p7MR19OyO1rcZKiYnNxP4s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=WCmis196; 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="WCmis196" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 529D1C4CEF1; Mon, 1 Dec 2025 21:24:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1764624283; bh=Diz0+bACmjM2TLHSfLwYpuxzqSwiJwi5SM5gyk06rTM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WCmis196wqbZY9mJ/hMHAC4BslWXP9ZhUHtY0YTPcr5qTh+qDb6vUY9v0d1Sb8kAB e1FhyuslxKKlhO8Viqa1Og+MxmReifTKIDv55qcujT8JG00VqvpT04AdvDixdSpjL5 WuXiHuHcb+vBwZ+ocU5qEjY+aWKOrn4+VVYUFHOHdiNKYnfPC5vCuGfK3Tv178olIt G3pS7SBEv8ZPYP42vp7mTmS05jfNtc2pqQMPy6+hTdU6MDsR6Aty8eLcWL+xDhd13S TM3bDnHbU8eYl2JaYFKJTQe+v0eKY6Ckgz+ILR34MbBtaUL7jJZvmmYTObWOhHNKh6 sHan9gM8tPErQ== Date: Mon, 1 Dec 2025 21:24:41 +0000 From: Jaegeuk Kim To: Matthew Wilcox Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-mm@kvack.org Subject: Re: [PATCH 3/4] mm/readahead: add a_ops->ra_folio_order to get a desired folio order Message-ID: References: <20251201210152.909339-1-jaegeuk@kernel.org> <20251201210152.909339-4-jaegeuk@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@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 12/01, Matthew Wilcox wrote: > On Mon, Dec 01, 2025 at 09:01:26PM +0000, Jaegeuk Kim wrote: > > This patch introduces a new address operation, a_ops->ra_folio_order(), which > > proposes a new folio order based on the adjusted order for page_cache_sync_ra. > > > > Hence, each filesystem can set the desired minimum order of folio allocation > > when requesting fadvise(POSIX_FADV_WILLNEED). > > Again, you've said what but not why. Does the mm code not ramp up the > folio order sufficiently quickly? What are you trying to accomplish? That's why I posted a series of the patches to provide more details. Could you please check the last patch in the series to show fadvise() does not increase the folio order? https://lore.kernel.org/linux-f2fs-devel/20251201210152.909339-5-jaegeuk@kernel.org/T/#u