diff options
author | Dave Chinner <dchinner@redhat.com> | 2015-01-21 23:10:26 +0100 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2015-01-21 23:10:26 +0100 |
commit | 4d11a40239405e531fc0e9dcd07921f00b965931 (patch) | |
tree | f8a6b43d76e4d698f7cb1a5daf9027d2a2f22ca7 /include | |
parent | Linux 3.19-rc1 (diff) | |
download | linux-4d11a40239405e531fc0e9dcd07921f00b965931.tar.xz linux-4d11a40239405e531fc0e9dcd07921f00b965931.zip |
xfs: remove bitfield based superblock updates
When we log changes to the superblock, we first have to write them
to the on-disk buffer, and then log that. Right now we have a
complex bitfield based arrangement to only write the modified field
to the buffer before we log it.
This used to be necessary as a performance optimisation because we
logged the superblock buffer in every extent or inode allocation or
freeing, and so performance was extremely important. We haven't done
this for years, however, ever since the lazy superblock counters
pulled the superblock logging out of the transaction commit
fast path.
Hence we have a bunch of complexity that is not necessary that makes
writing the in-core superblock to disk much more complex than it
needs to be. We only need to log the superblock now during
management operations (e.g. during mount, unmount or quota control
operations) so it is not a performance critical path anymore.
As such, remove the complex field based logging mechanism and
replace it with a simple conversion function similar to what we use
for all other on-disk structures.
This means we always log the entirity of the superblock, but again
because we rarely modify the superblock this is not an issue for log
bandwidth or CPU time. Indeed, if we do log the superblock
frequently, delayed logging will minimise the impact of this
overhead.
[Fixed gquota/pquota inode sharing regression noticed by bfoster.]
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions