diff options
author | Darrick J. Wong <djwong@kernel.org> | 2022-04-26 03:37:15 +0200 |
---|---|---|
committer | Darrick J. Wong <djwong@kernel.org> | 2022-04-28 19:24:59 +0200 |
commit | 4ed6435cc369cce722966983f6e07b872562276f (patch) | |
tree | 0ad8014350e4608cb9ceb455cb835f88dfd9c211 /scripts/Makefile.gcc-plugins | |
parent | xfs: count EFIs when deciding to ask for a continuation of a refcount update (diff) | |
download | linux-4ed6435cc369cce722966983f6e07b872562276f.tar.xz linux-4ed6435cc369cce722966983f6e07b872562276f.zip |
xfs: stop artificially limiting the length of bunmap calls
In commit e1a4e37cc7b6, we clamped the length of bunmapi calls on the
data forks of shared files to avoid two failure scenarios: one where the
extent being unmapped is so sparsely shared that we exceed the
transaction reservation with the sheer number of refcount btree updates
and EFI intent items; and the other where we attach so many deferred
updates to the transaction that we pin the log tail and later the log
head meets the tail, causing the log to livelock.
We avoid triggering the first problem by tracking the number of ops in
the refcount btree cursor and forcing a requeue of the refcount intent
item any time we think that we might be close to overflowing. This has
been baked into XFS since before the original e1a4 patch.
A recent patchset fixed the second problem by changing the deferred ops
code to finish all the work items created by each round of trying to
complete a refcount intent item, which eliminates the long chains of
deferred items (27dad); and causing long-running transactions to relog
their intent log items when space in the log gets low (74f4d).
Because this clamp affects /any/ unmapping request regardless of the
sharing factors of the component blocks, it degrades the performance of
all large unmapping requests -- whereas with an unshared file we can
unmap millions of blocks in one go, shared files are limited to
unmapping a few thousand blocks at a time, which causes the upper level
code to spin in a bunmapi loop even if it wasn't needed.
This also eliminates one more place where log recovery behavior can
differ from online behavior, because bunmapi operations no longer need
to requeue. The fstest generic/447 was created to test the old fix, and
it still passes with this applied.
Partial-revert-of: e1a4e37cc7b6 ("xfs: try to avoid blowing out the transaction reservation when bunmaping a shared extent")
Depends: 27dada070d59 ("xfs: change the order in which child and parent defer ops ar finished")
Depends: 74f4d6a1e065 ("xfs: only relog deferred intent items if free space in the log gets low")
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'scripts/Makefile.gcc-plugins')
0 files changed, 0 insertions, 0 deletions