diff options
author | Darrick J. Wong <darrick.wong@oracle.com> | 2019-04-15 13:13:21 -0700 |
---|---|---|
committer | Darrick J. Wong <darrick.wong@oracle.com> | 2019-04-16 10:01:58 -0700 |
commit | 3994fc48957520df061990ed22fff96023cfd953 (patch) | |
tree | 4b2bd3b7544bbbbfc3223bc1b586f6f50e3e27cd /lib/crc16.c | |
parent | 28408243706e1ec137876154ea212a1316db399a (diff) |
xfs: merge adjacent io completions of the same type
It's possible for pagecache writeback to split up a large amount of work
into smaller pieces for throttling purposes or to reduce the amount of
time a writeback operation is pending. Whatever the reason, XFS can end
up with a bunch of IO completions that call for the same operation to be
performed on a contiguous extent mapping. Since mappings are extent
based in XFS, we'd prefer to run fewer transactions when we can.
When we're processing an ioend on the list of io completions, check to
see if the next items on the list are both adjacent and of the same
type. If so, we can merge the completions to reduce transaction
overhead.
On fast storage this doesn't seem to make much of a difference in
performance, though the number of transactions for an overnight xfstests
run seems to drop by ~5%.
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Diffstat (limited to 'lib/crc16.c')
0 files changed, 0 insertions, 0 deletions