All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: lttng-dev@lists.lttng.org
Subject: [PATCH lttng-modules 2/3] Add btrfs file item tracepoints
Date: Thu,  7 Jun 2018 15:48:31 -0400	[thread overview]
Message-ID: <20180607194832.20578-2-mjeanson__38542.4034357586$1528400821$gmane$org@efficios.com> (raw)
In-Reply-To: <20180607194832.20578-1-mjeanson@efficios.com>

See upstream commit:

  commit 09ed2f165cb3449237dec842b3564044e12d22cb
  Author: Liu Bo <bo.li.liu@oracle.com>
  Date:   Fri Mar 10 11:09:48 2017 -0800

    Btrfs: add file item tracepoints

    While debugging truncate problems, I found that these tracepoints could
    help us quickly know what went wrong.

    Two sets of tracepoints are created to track regular/prealloc file item
    and inline file item respectively, I put inline as a separate one since
    what inline file items cares about are way less than the regular one.

    This adds four tracepoints:
    - btrfs_get_extent_show_fi_regular
    - btrfs_get_extent_show_fi_inline
    - btrfs_truncate_show_fi_regular
    - btrfs_truncate_show_fi_inline

Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
---
 instrumentation/events/lttng-module/btrfs.h | 83 +++++++++++++++++++++
 1 file changed, 83 insertions(+)

diff --git a/instrumentation/events/lttng-module/btrfs.h b/instrumentation/events/lttng-module/btrfs.h
index c413e92..6ef21e0 100644
--- a/instrumentation/events/lttng-module/btrfs.h
+++ b/instrumentation/events/lttng-module/btrfs.h
@@ -291,6 +291,89 @@ LTTNG_TRACEPOINT_EVENT(btrfs_handle_em_exist,
 )
 #endif
 
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,12,0))
+LTTNG_TRACEPOINT_EVENT_CLASS(btrfs__file_extent_item_regular,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, u64 start),
+
+	TP_ARGS(bi, l, fi, start),
+
+	TP_FIELDS(
+		ctf_array(u8, fsid, bi->root->fs_info, BTRFS_FSID_SIZE)
+		ctf_integer(u64, root_obj, bi->root->objectid)
+		ctf_integer(u64, ino, btrfs_ino(bi))
+		ctf_integer(loff_t, isize, bi->vfs_inode.i_size)
+		ctf_integer(u64, disk_isize, bi->disk_i_size)
+		ctf_integer(u64, num_bytes, btrfs_file_extent_num_bytes(l, fi))
+		ctf_integer(u64, ram_bytes, btrfs_file_extent_ram_bytes(l, fi))
+		ctf_integer(u64, disk_bytenr, btrfs_file_extent_disk_bytenr(l, fi))
+		ctf_integer(u64, disk_num_bytes, btrfs_file_extent_disk_num_bytes(l, fi))
+		ctf_integer(u64, extent_offset, btrfs_file_extent_offset(l, fi))
+		ctf_integer(u8, extent_type, btrfs_file_extent_type(l, fi))
+		ctf_integer(u8, compression, btrfs_file_extent_compression(l, fi))
+		ctf_integer(u64, extent_start, start)
+		ctf_integer(u64, extent_end, (start + btrfs_file_extent_num_bytes(l, fi)))
+	)
+)
+
+LTTNG_TRACEPOINT_EVENT_CLASS(btrfs__file_extent_item_inline,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, int slot, u64 start),
+
+	TP_ARGS(bi, l, fi, slot, start),
+
+	TP_FIELDS(
+		ctf_array(u8, fsid, bi->root->fs_info, BTRFS_FSID_SIZE)
+		ctf_integer(u64, root_obj, bi->root->objectid)
+		ctf_integer(u64, ino, btrfs_ino(bi))
+		ctf_integer(loff_t, isize, bi->vfs_inode.i_size)
+		ctf_integer(u64, disk_isize, bi->disk_i_size)
+		ctf_integer(u8, extent_type, btrfs_file_extent_type(l, fi))
+		ctf_integer(u8, compression, btrfs_file_extent_compression(l, fi))
+		ctf_integer(u64, extent_start, start)
+		ctf_integer(u64, extent_end, (start + btrfs_file_extent_inline_len(l, slot, fi)))
+	)
+)
+
+LTTNG_TRACEPOINT_EVENT_INSTANCE(
+	btrfs__file_extent_item_regular, btrfs_get_extent_show_fi_regular,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, u64 start),
+
+	TP_ARGS(bi, l, fi, start)
+)
+
+LTTNG_TRACEPOINT_EVENT_INSTANCE(
+	btrfs__file_extent_item_regular, btrfs_truncate_show_fi_regular,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, u64 start),
+
+	TP_ARGS(bi, l, fi, start)
+)
+
+LTTNG_TRACEPOINT_EVENT_INSTANCE(
+	btrfs__file_extent_item_inline, btrfs_get_extent_show_fi_inline,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, int slot, u64 start),
+
+	TP_ARGS(bi, l, fi, slot, start)
+)
+
+LTTNG_TRACEPOINT_EVENT_INSTANCE(
+	btrfs__file_extent_item_inline, btrfs_truncate_show_fi_inline,
+
+	TP_PROTO(struct btrfs_inode *bi, struct extent_buffer *l,
+		 struct btrfs_file_extent_item *fi, int slot, u64 start),
+
+	TP_ARGS(bi, l, fi, slot, start)
+)
+#endif
+
 #if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,14,0))
 LTTNG_TRACEPOINT_EVENT_CLASS(btrfs__ordered_extent,
 
-- 
2.17.1

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

       reply	other threads:[~2018-06-07 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180607194832.20578-1-mjeanson@efficios.com>
2018-06-07 19:48 ` Michael Jeanson [this message]
2018-06-07 19:48 ` [PATCH lttng-modules 3/3] Update delayed ref tracepoints for v3.12 Michael Jeanson
2018-06-07 20:11 ` [PATCH lttng-modules 1/3] Add btrfs tracepoint for em's EEXIST case Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='20180607194832.20578-2-mjeanson__38542.4034357586$1528400821$gmane$org@efficios.com' \
    --to=mjeanson@efficios.com \
    --cc=lttng-dev@lists.lttng.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.