filemap: allocate mapping_min_order folios in the page cache
authorPankaj Raghav <p.raghav@samsung.com>
Thu, 22 Aug 2024 13:50:10 +0000 (15:50 +0200)
committerChristian Brauner <brauner@kernel.org>
Fri, 23 Aug 2024 11:49:48 +0000 (13:49 +0200)
commitab95d23bab220ef845c0d422f49452a475330eaf
treed9afa7c6086649ef33703800e7a059a33562c5b3
parent84429b675bcfd2a518ae167ee4661cdf7539aa7d
filemap: allocate mapping_min_order folios in the page cache

filemap_create_folio() and do_read_cache_folio() were always allocating
folio of order 0. __filemap_get_folio was trying to allocate higher
order folios when fgp_flags had higher order hint set but it will default
to order 0 folio if higher order memory allocation fails.

Supporting mapping_min_order implies that we guarantee each folio in the
page cache has at least an order of mapping_min_order. When adding new
folios to the page cache we must also ensure the index used is aligned to
the mapping_min_order as the page cache requires the index to be aligned
to the order of the folio.

Co-developed-by: Luis Chamberlain <mcgrof@kernel.org>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
Link: https://lore.kernel.org/r/20240822135018.1931258-3-kernel@pankajraghav.com
Tested-by: David Howells <dhowells@redhat.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: Daniel Gomez <da.gomez@samsung.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Christian Brauner <brauner@kernel.org>
include/linux/pagemap.h
mm/filemap.c