Darrick J. Wong 036f463fe1 xfs: online scrub needn't bother zeroing its temporary buffer ... The xattr scrubber functions use the temporary memory buffer either for storing bitmaps or for testing if attribute value extraction works. The bitmap code always zeroes what it needs and the value extraction sets the buffer contents, so it's not necessary to waste CPU time zeroing on allocation. Note that while we never read the contents that the attr value extraction function sets, we do need to call it to check the remote attribute header and CRCs to check for corruption. A flame graph analysis showed that we were spending 7% of a xfs_scrub run (the whole program, not just the attr scrubber itself) allocating and zeroing 64k segments needlessly. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Brian Foster <bfoster@redhat.com>		2019-07-05 10:29:56 -07:00
..
agheader_repair.c
agheader.c
alloc.c
attr.c	xfs: online scrub needn't bother zeroing its temporary buffer	2019-07-05 10:29:56 -07:00
attr.h	xfs: only allocate memory for scrubbing attributes when we need it	2019-07-05 10:29:56 -07:00
bitmap.c
bitmap.h
bmap.c
btree.c
btree.h
common.c
common.h
dabtree.c
dabtree.h
dir.c
fscounters.c
health.c
health.h
ialloc.c
inode.c
parent.c
quota.c
refcount.c
repair.c
repair.h
rmap.c
rtbitmap.c
scrub.c
scrub.h
symlink.c
trace.c
trace.h
xfs_scrub.h