From: Pankaj Raghav <p.raghav@xxxxxxxxxxx> This is the first version of the series(2 RFCs posted before) that enables block size > page size(Large Block Size) in XFS. This version has various bug fixes and suggestion collected from previous RFCs[1][2]. The context and motivation can be seen in cover letter of the RFC v1[1]. We also recorded a talk about this effort at LPC [3], if someone would like more context on this effort. A lot of emphasis has been put on testing using kdevops. The testing has been split into regression and progression. Regression testing: In regression testing, we ran the whole test suite with SOAK_DURATION=2.5 hours to check for *regression on existing profiles due to the page cache changes. No regression was found with the patches added on top. *Baseline for regression was created using SOAK_DURATION of 2.5 hours and having used about 7-8 XFS test clusters to test loop fstests over 70 times. We then scraped for critical failures (crashes, XFS or page cache asserts, or hung tasks) and have reported these to the community as well.[5] Progression testing: For progression testing, we tested for 8k, 16k, 32k and 64k block sizes. To compare it with existing support, an ARM VM with 64k base page system (without our patches) was used as a reference to check for actual failures due to LBS support in a 4k base page size system. There are some common failures upstream for bs=64k that needs to be fixed[4]. There are also some tests that assumes block size < page size that needs to be fixed. I have a tree with fixes for xfstests here [6], which I will be sending soon to the list. No new failures were found with LBS support. We've done some preliminary performance tests with fio on XFS on 4k block size against pmem and NVMe with buffered IO and Direct IO on vanilla v6.8-rc4 Vs v6.8-rc4 + these patches applied, and detected no regressions. We also wrote an eBPF tool called blkalgn [7] to see if IO sent to the device is aligned and at least filesystem block size in length. I have also started the discussion with Zi Yan to upstream truncation with lower folio order that will improve the memory utilization when partial truncate happens with LBS support(Patch 9).[8] The series has been greatly improved (and simplified) since the previous version. Thanks to Chinner, Darrick, Hannes and willy for your comments. [1] https://lore.kernel.org/lkml/20230915183848.1018717-1-kernel@xxxxxxxxxxxxxxxx/ [2] https://lore.kernel.org/linux-xfs/20240213093713.1753368-1-kernel@xxxxxxxxxxxxxxxx/ [3] https://www.youtube.com/watch?v=ar72r5Xf7x4 [4] https://github.com/linux-kdevops/kdevops/blob/master/docs/xfs-bugs.md 489 non-critical issues and 55 critical issues. We've determined and reported that the 55 critical issues have all fall into 5 common XFS asserts or hung tasks and 2 memory management asserts. [5] https://lore.kernel.org/linux-xfs/fe7fec1c-3b08-430f-9c95-ea76b237acf4@xxxxxxxxxxx/ [6] https://github.com/Panky-codes/xfstests/tree/lbs-fixes [7] https://github.com/iovisor/bcc/pull/4813 [8] https://lore.kernel.org/all/dvamjmlss62p5pf4das7nu5q35ftf4jlk3viwzyyvzasv4qjns@h3omqs7ecstd/ Changes since RFC v2: - Move order 1 patch above the 1st patch - Remove order == 1 conditional in `fs: Allow fine-grained control of folio sizes`. This fixed generic/630 that was reported in the previous version. - Hide the max order and expose `mapping_set_folio_min_order` instead. - Add new helper mapping_start_index_align and DEFINE_READAHEAD_ALIGN - don't call `page_cache_ra_order` with min order in do_mmap_sync_readahead - simplify ondemand readahead with only aligning the start index at the end - Don't cap ra_pages based on bdi->io_pages - use `checked_mul_overflow` while calculating bytes in validate_fsb - Remove config lbs option - Add a warning while mounting a LBS kernel - Add Acked-by and Reviewed-by from Hannes and Darrick. Changes since RFC v1: - Added willy's patch to enable order-1 folios. - Unified common page cache effort from Hannes LBS work. - Added a new helper min_nrpages and added CONFIG_THP for enabling mapping_large_folio_support - Don't split a folio if it has minorder set. Remove the old code where we set extra pins if it has that requirement. - Split the code in XFS between the validation of mapping count. Put the icache code changes with enabling bs > ps. - Added CONFIG_XFS_LBS option - align the index in do_read_cache_folio() - Removed truncate changes - Fixed generic/091 with iomap changes to iomap_dio_zero function. - Took care of folio truncation scenario in page_cache_ra_unbounded() that happens after read_pages if a folio was found. - Sqaushed and moved commits around - Rebased on top of v6.8-rc4 Dave Chinner (1): xfs: expose block size in stat Hannes Reinecke (1): readahead: rework loop in page_cache_ra_unbounded() Luis Chamberlain (3): filemap: align the index to mapping_min_order in the page cache readahead: set file_ra_state->ra_pages to be at least mapping_min_order readahead: align index to mapping_min_order in ondemand_ra and force_ra Matthew Wilcox (Oracle) (2): mm: Support order-1 folios in the page cache fs: Allow fine-grained control of folio sizes Pankaj Raghav (6): filemap: use mapping_min_order while allocating folios readahead: allocate folios with mapping_min_order in ra_(unbounded|order) mm: do not split a folio if it has minimum folio order requirement iomap: fix iomap_dio_zero() for fs bs > system page size xfs: make the calculation generic in xfs_sb_validate_fsb_count() xfs: enable block size larger than page size support fs/iomap/direct-io.c | 13 ++++- fs/xfs/libxfs/xfs_ialloc.c | 5 ++ fs/xfs/libxfs/xfs_shared.h | 3 ++ fs/xfs/xfs_icache.c | 6 ++- fs/xfs/xfs_iops.c | 2 +- fs/xfs/xfs_mount.c | 9 +++- fs/xfs/xfs_super.c | 10 +--- include/linux/huge_mm.h | 7 ++- include/linux/pagemap.h | 108 ++++++++++++++++++++++++++++++------- mm/filemap.c | 48 +++++++++++------ mm/huge_memory.c | 36 +++++++++++-- mm/internal.h | 4 +- mm/readahead.c | 74 ++++++++++++++++++------- 13 files changed, 246 insertions(+), 79 deletions(-) base-commit: b401b621758e46812da61fa58a67c3fd8d91de0d -- 2.43.0
