diff options
| author | Christoph Hellwig <hch@lst.de> | 2022-06-21 09:49:44 +0200 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-07-25 17:45:37 +0200 |
| commit | f3e90c1ca93d18d03188ea2c2ca9c2ccc7ffad04 (patch) | |
| tree | 6108a181b3629aa782d021f3b517e525207d85da /fs/btrfs/subpage.c | |
| parent | 9555e1f1887f4ac2c106f2ea8b8b7f4c93a91b9b (diff) | |
| download | linux-f3e90c1ca93d18d03188ea2c2ca9c2ccc7ffad04.tar.gz linux-f3e90c1ca93d18d03188ea2c2ca9c2ccc7ffad04.tar.bz2 linux-f3e90c1ca93d18d03188ea2c2ca9c2ccc7ffad04.zip | |
btrfs: remove extent writepage address space operation
Same as in commit 21b4ee7029c9 ("xfs: drop ->writepage completely"): we
can remove the callback as it's only used in one place - single page
writeback from memory reclaim and is not called for cgroup writeback at
all.
We only allow such writeback from kswapd, not from direct memory
reclaim, and so it is rarely used. When it comes from kswapd, it is
effectively random dirty page shoot-down, which is horrible for IO
patterns. We can rely on background writeback to clean all dirty pages
in an efficient way and not let it be interrupted by kswapd.
Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/subpage.c')
| -rw-r--r-- | fs/btrfs/subpage.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/subpage.c b/fs/btrfs/subpage.c index 0146fee730a0..6fc2b77ae5c3 100644 --- a/fs/btrfs/subpage.c +++ b/fs/btrfs/subpage.c @@ -731,7 +731,7 @@ void btrfs_page_assert_not_dirty(const struct btrfs_fs_info *fs_info, * It should not have any subpage::writers count. * Can be unlocked by unlock_page(). * This is the most common locked page for __extent_writepage() called - * inside extent_write_cache_pages() or extent_write_full_page(). + * inside extent_write_cache_pages(). * Rarer cases include the @locked_page from extent_write_locked_range(). * * - Page locked by lock_delalloc_pages() |