aboutsummaryrefslogtreecommitdiffstats
path: root/fs/btrfs/compression.c
diff options
context:
space:
mode:
authorQu Wenruo <[email protected]>2025-03-26 02:54:21 +0000
committerDavid Sterba <[email protected]>2025-05-15 12:30:40 +0000
commitbe8ef7990c6775c2bb1374abbde8f5408c527eba (patch)
tree02fc7adec8d89c8c5dbad83c3da2bd1b4fcb35c3 /fs/btrfs/compression.c
parentbtrfs: refactor how we handle reserved space inside copy_one_range() (diff)
downloadkernel-be8ef7990c6775c2bb1374abbde8f5408c527eba.tar.gz
kernel-be8ef7990c6775c2bb1374abbde8f5408c527eba.zip
btrfs: prepare btrfs_buffered_write() for large data folios
This involves the following modifications: - Set the order flags for __filemap_get_folio() inside prepare_one_folio() This will allow __filemap_get_folio() to create a large folio if the address space supports it. - Limit the initial @write_bytes inside copy_one_range() If the largest folio boundary splits the initial write range, there is no way we can write beyond the largest folio boundary. This is done by a simple helper calc_write_bytes(). - Release exceeding reserved space if the folio is smaller than expected Which is doing the same handling when short copy happens. All the preparations should not change the behavior when the largest folio order is 0. Reviewed-by: Filipe Manana <[email protected]> Signed-off-by: Qu Wenruo <[email protected]> Signed-off-by: David Sterba <[email protected]>
Diffstat (limited to 'fs/btrfs/compression.c')
0 files changed, 0 insertions, 0 deletions