]> git.ipfire.org Git - thirdparty/xfsprogs-dev.git/commit
xfs: add kmem allocation trace points
authorDave Chinner <dchinner@redhat.com>
Fri, 15 Nov 2019 22:16:21 +0000 (17:16 -0500)
committerEric Sandeen <sandeen@redhat.com>
Fri, 15 Nov 2019 22:16:21 +0000 (17:16 -0500)
commitb7b3456e4157803bd1e6800ad44f97eaeae6fc2d
treea7d6e2cda7af48146bf69ce4f1cc6ea0b72a27fb
parent149850bd9d6642d2feeaee25ef45b659e679e13c
xfs: add kmem allocation trace points

Source kernel commit: 0ad95687c3adb91e762d0f6ea50a6b1137300e19

When trying to correlate XFS kernel allocations to memory reclaim
behaviour, it is useful to know what allocations XFS is actually
attempting. This information is not directly available from
tracepoints in the generic memory allocation and reclaim
tracepoints, so these new trace points provide a high level
indication of what the XFS memory demand actually is.

There is no per-filesystem context in this code, so we just trace
the type of allocation, the size and the allocation constraints.
The kmem code also doesn't include much of the common XFS headers,
so there are a few definitions that need to be added to the trace
headers and a couple of types that need to be made common to avoid
needing to include the whole world in the kmem code.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Eric Sandeen <sandeen@sandeen.net
include/xfs_mount.h
libxfs/xfs_types.h