On Mon, Feb 05, 2018 at 12:46:00PM -0500, Brian Foster wrote: > The AGFL perag reservation type accounts all allocations that feed > into (or are released from) the allocation group free list (agfl). > The purpose of the reservation is to support worst case conditions > for the reverse mapping btree (rmapbt). As such, the agfl > reservation usage accounting only considers rmapbt usage when the > in-core counters are initialized at mount time. > > This implementation inconsistency leads to divergence of the in-core > and on-disk usage accounting over time. In preparation to resolve > this inconsistency and adjust the AGFL reservation into an rmapbt > specific reservation, rename the AGFL reservation type and > associated accounting fields to something more rmapbt-specific. Also > fix up a couple tracepoints that incorrectly use the AGFL > reservation type to pass the agfl state of the associated extent > where the raw reservation type is expected. > > Note that this patch does not change perag reservation behavior. > > Signed-off-by: Brian Foster <bfoster@xxxxxxxxxx> Looks ok, though the tracepoint fix should probably be a standalone patch. Reviewed-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> --D -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
