diff options
author | Serapheim Dimitropoulos <[email protected]> | 2019-09-06 01:57:55 +0900 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2019-09-05 09:57:55 -0700 |
commit | 65a91b166e66a57c44b62bb5ca20ccb6f0ecc46d (patch) | |
tree | cf23826054ca86f49c16b6bc240ef64e2131d544 /config/kernel-truncate-range.m4 | |
parent | 240c015ac6ea629bef1339ed2829148051c2a954 (diff) |
metaslab_verify_weight_and_frag() shouldn't cause side-effects
`metaslab_verify_weight_and_frag()` a verification function and
by the end of it there shouldn't be any side-effects.
The function calls `metaslab_weight()` which in turn calls
`metaslab_set_fragmentation()`. The latter can dirty and otherwise
not dirty metaslab fro the next TXGand set `metaslab_condense_wanted`
if the spacemaps were just upgraded (meaning we just enabled the
SPACEMAP_HISTOGRAM feature through upgrade).
This patch adds a new flag as a parameter to `metaslab_weight()` and
`metaslab_set_fragmentation()` making the dirtying of the metaslab
optional.
Reviewed-by: Matt Ahrens <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Serapheim Dimitropoulos <[email protected]>
Closes #9185
Closes #9282
Diffstat (limited to 'config/kernel-truncate-range.m4')
0 files changed, 0 insertions, 0 deletions