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 35C46184524 for ; Mon, 1 Dec 2025 21:20:03 +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=1764624005; cv=none; b=XNCdzUKeSnaKYPmSPorS9k2Pcqi/fvtkfaTj5cIRJitIeeihxocbYq3FEXODOrjqmZ6rTtmlJwW98pntMNIOXIShmCfZf8GXrD5y+ORCwejRLSgI7EOioQdUOgArI430MUxV5i14WFSxsP/UYcRNOPl+gZKBIVzFWoxlNzbgHts= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764624005; c=relaxed/simple; bh=+LWAL5hfRKfiJiyRffv0dJXWh8PCnHJl1/yexYhriyg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IYNGN+D33nWbc2/l8uS8J7RJ9ge4nX9SiMKk2tvbcpOLnsGdwdAGtuEBXIVDdkpIuvJHfrRH8+/NLxtKvzF5t8Huel0AwD+qGiwmF0EyUdfHI8Jf18wFv1NndqUuPxiRbbHU9i/HDc4U1cq3uBAlawrNHgTYL7mQJ+vsixvvu3c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=v/1wqjVQ; 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=none 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="v/1wqjVQ" 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=WiTdOzM04TmD+7whCaojUYm7mGYFeydQ5w051q8EpM8=; b=v/1wqjVQuVqUG/+O5g8v+0grIj P1nnzXYsylJ3+vn50/5fcldCEWTjr1aELVUcxaJQtNsdoQBhsvwSpjTJo6XJdZTKhHeTHF2fKwvPL Fj8jVOeuyZt9q3M6YcJ4CVd4CWZHUZtkx65fKuQfkRCAEXo18n7VA/h+o2haxIwvapGJGUtayaSw4 N/z3YzyeJBiFIDDR5zHljspUkRY9iOrT5N80nvesmtQA5c08KSEWOITB7oIqsblySL7IRXxyHa7iU yhEqJxI0XnsbO5RLFr2AQW2hqZVoKCrs/3AEe6E47E8e6QIq32Cq/s76VbiSVgeBqhxp+dQupk6FN a2C/6frA==; Received: from willy by casper.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1vQBJR-00000000FYG-1Pcz; Mon, 01 Dec 2025 21:20:01 +0000 Date: Mon, 1 Dec 2025 21:20:01 +0000 From: Matthew Wilcox To: Jaegeuk Kim 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: <20251201210152.909339-4-jaegeuk@kernel.org> 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?