From: Julian Sun <sunjunchao2870@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-trace-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, brauner@kernel.org,
viro@zeniv.linux.org.uk, mhiramat@kernel.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com
Subject: Re: [PATCH] writeback: Refine the show_inode_state() macro definition
Date: Wed, 28 Aug 2024 15:44:10 +0800 [thread overview]
Message-ID: <9e9f7e7eb26dd312df1208ae5771c0bf6acf7730.camel@gmail.com> (raw)
In-Reply-To: <20240827162150.rzgnguesq44yqd57@quack3>
On Tue, 2024-08-27 at 18:21 +0200, Jan Kara wrote:
> On Tue 20-08-24 17:52:29, Julian Sun wrote:
> > Currently, the show_inode_state() macro only prints
> > part of the state of inode->i_state. Let’s improve it
> > to display more of its state.
> >
> > Signed-off-by: Julian Sun <sunjunchao2870@gmail.com>
> > ---
> > include/trace/events/writeback.h | 11 ++++++++++-
> > 1 file changed, 10 insertions(+), 1 deletion(-)
>
> Yeah, it could be useful at times. Some comments below.
>
> > @@ -20,7 +20,16 @@
> > {I_CLEAR, "I_CLEAR"}, \
> > {I_SYNC, "I_SYNC"}, \
> > {I_DIRTY_TIME, "I_DIRTY_TIME"}, \
> > - {I_REFERENCED, "I_REFERENCED"} \
> > + {I_REFERENCED, "I_REFERENCED"}, \
> > + {I_DIO_WAKEUP, "I_DIO_WAKEUP"}, \
>
> I_DIO_WAKEUP is never set and is being removed, please don't put it
> here.
>
> > + {I_LINKABLE, "I_LINKABLE"}, \
> > + {I_DIRTY_TIME, "I_DIRTY_TIME"}, \
>
> Um, I_DIRTY_TIME is already included.
>
> > + {I_WB_SWITCH, "I_WB_SWITCH"}, \
> > + {I_OVL_INUSE, "I_OVL_INUSE"}, \
> > + {I_CREATING, "I_CREATING"}, \
> > + {I_DONTCACHE, "I_DONTCACHE"}, \
> > + {I_SYNC_QUEUED, "I_SYNC_QUEUED"}, \
> > + {I_PINNING_NETFS_WB, "I_PINNING_NETFS_WB"} \
> > )
>
> Otherwise the patch looks good to me.
Thanks for your review and comments, I will fix them in patch v2.
>
> Honza
Thanks,
--
Julian Sun <sunjunchao2870@gmail.com>
next prev parent reply other threads:[~2024-08-28 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 9:52 [PATCH] writeback: Refine the show_inode_state() macro definition Julian Sun
2024-08-27 16:21 ` Jan Kara
2024-08-28 7:44 ` Julian Sun [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-20 9:49 Julian Sun
2024-08-20 9:54 ` Julian Sun
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=9e9f7e7eb26dd312df1208ae5771c0bf6acf7730.camel@gmail.com \
--to=sunjunchao2870@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
/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).