From: Steven Rostedt <rostedt@goodmis.org>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
"Theodore Ts'o" <tytso@mit.edu>,
Harshad Shirwadkar <harshadshirwadkar@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 00/10] ext4: Improve FC trace events
Date: Thu, 10 Mar 2022 19:39:36 -0500 [thread overview]
Message-ID: <20220310193936.38ae7754@gandalf.local.home> (raw)
In-Reply-To: <20220310170731.hq6z6flycmgkhnaa@riteshh-domain>
On Thu, 10 Mar 2022 22:37:31 +0530
Ritesh Harjani <riteshh@linux.ibm.com> wrote:
> On 22/03/10 11:05AM, Steven Rostedt wrote:
> > On Thu, 10 Mar 2022 21:28:54 +0530
> > Ritesh Harjani <riteshh@linux.ibm.com> wrote:
> >
> > > Note:- I still couldn't figure out how to expose EXT4_FC_REASON_MAX in patch-2
> > > which (I think) might be (only) needed by trace-cmd or perf record for trace_ext4_fc_stats.
> > > But it seems "cat /sys/kernel/debug/tracing/trace_pipe" gives the right output
> > > for ext4_fc_stats trace event (as shown below).
> > >
> > > So with above reasoning, do you think we should take these patches in?
> > > And we can later see how to provide EXT4_FC_REASON_MAX definition available to
> > > libtraceevent?
> >
> > I don't see EXT4_FC_REASON_MAX being used in the TP_printk(). If it isn't
> > used there, it doesn't need to be exposed. Or did I miss something?
>
> I was mentioning about EXT4_FC_REASON_MAX used in TP_STRUCT__entry.
> When I hard code EXT4_FC_REASON_MAX to 9 in TP_STRUCT__entry, I could
> see proper values using trace-cmd. Otherwise I see all 0 (when using trace-cmd
> or perf record).
>
> + TP_STRUCT__entry(
> + __field(dev_t, dev)
> + __array(unsigned int, fc_ineligible_rc, EXT4_FC_REASON_MAX)
Ah, I bet it's showing up in the format portion and not the print fmt part
of the format file.
Just to confirm, can you do the following:
# cat /sys/kernel/tracing/events/ext4/ext4_fc_commit_stop/format
and show me what it outputs.
Thanks,
-- Steve
>
> Should we anyway hard code this to 9. Since we are anyway printing all the
> 9 elements of array values individually.
>
> + TP_printk("dev %d,%d fc ineligible reasons:\n"
> + "%s:%u, %s:%u, %s:%u, %s:%u, %s:%u, %s:%u, %s:%u, %s:%u, %s:%u "
> + "num_commits:%lu, ineligible: %lu, numblks: %lu",
> + MAJOR(__entry->dev), MINOR(__entry->dev),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_XATTR),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_CROSS_RENAME),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_JOURNAL_FLAG_CHANGE),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_NOMEM),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_SWAP_BOOT),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_RESIZE),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_RENAME_DIR),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_FALLOC_RANGE),
> + FC_REASON_NAME_STAT(EXT4_FC_REASON_INODE_JOURNAL_DATA),
> + __entry->fc_commits, __entry->fc_ineligible_commits,
> + __entry->fc_numblks)
>
>
> Thanks
> -ritesh
next prev parent reply other threads:[~2022-03-11 0:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 15:58 [PATCHv2 00/10] ext4: Improve FC trace events Ritesh Harjani
2022-03-10 15:58 ` [PATCHv2 01/10] ext4: Remove unused enum EXT4_FC_COMMIT_FAILED Ritesh Harjani
2022-03-10 15:58 ` [PATCHv2 02/10] ext4: Fix ext4_fc_stats trace point Ritesh Harjani
2022-03-10 15:58 ` [PATCHv2 03/10] ext4: Convert ext4_fc_track_dentry type events to use event class Ritesh Harjani
2022-03-10 15:58 ` [PATCHv2 04/10] ext4: Do not call FC trace event in ext4_fc_commit() if FS does not support FC Ritesh Harjani
2022-03-10 15:58 ` [PATCHv2 05/10] ext4: Return early for non-eligible fast_commit track events Ritesh Harjani
2022-03-10 15:59 ` [PATCHv2 06/10] ext4: Add new trace event in ext4_fc_cleanup Ritesh Harjani
2022-03-10 15:59 ` [PATCHv2 07/10] ext4: Add transaction tid info in fc_track events Ritesh Harjani
2022-03-10 15:59 ` [PATCHv2 08/10] ext4: Add commit_tid info in jbd debug log Ritesh Harjani
2022-03-10 15:59 ` [PATCHv2 09/10] ext4: Add commit tid info in ext4_fc_commit_start/stop trace events Ritesh Harjani
2022-03-10 15:59 ` [PATCHv2 10/10] ext4: Fix remaining two trace events to use same printk convention Ritesh Harjani
2022-03-10 16:05 ` [PATCHv2 00/10] ext4: Improve FC trace events Steven Rostedt
2022-03-10 17:07 ` Ritesh Harjani
2022-03-11 0:39 ` Steven Rostedt [this message]
2022-03-11 2:19 ` Ritesh Harjani
2022-03-11 2:33 ` Steven Rostedt
2022-03-11 3:14 ` Ritesh Harjani
2022-03-11 4:32 ` Steven Rostedt
2022-03-11 5:12 ` Ritesh Harjani
2022-03-11 14:45 ` Steven Rostedt
2022-03-11 15:03 ` Ritesh Harjani
2022-03-11 16:42 ` Steven Rostedt
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=20220310193936.38ae7754@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=harshadshirwadkar@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).