linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julian Sun <sunjunchao2870@gmail.com>
To: linux-trace-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: jack@suse.cz, 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: Tue, 20 Aug 2024 17:54:44 +0800	[thread overview]
Message-ID: <CAHB1NagnXCDh_dVMX7TLBamtyF+G_1Ug0vohQg+jkJs8e2RuGg@mail.gmail.com> (raw)
In-Reply-To: <20240820094922.375996-1-sunjunchao2870@gmail.com>

Apologies, this patch was sent by mistake. Please refer to the latest patch

Julian Sun <sunjunchao2870@gmail.com> 于2024年8月20日周二 17:49写道:
>
> 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 | 9 +++++++++
>  1 file changed, 9 insertions(+)
>
> diff --git a/include/trace/events/writeback.h b/include/trace/events/writeback.h
> index 54e353c9f919..a2c2bb1cddd7 100644
> --- a/include/trace/events/writeback.h
> +++ b/include/trace/events/writeback.h
> @@ -21,6 +21,15 @@
>                 {I_SYNC,                "I_SYNC"},              \
>                 {I_DIRTY_TIME,          "I_DIRTY_TIME"},        \
>                 {I_REFERENCED,          "I_REFERENCED"}         \
> +               {I_DIO_WAKEUP,  "I_DIO_WAKEUP"} \
> +               {I_LINKABLE,    "I_LINKABLE"}   \
> +               {I_DIRTY_TIME,  "I_DIRTY_TIME"} \
> +               {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"} \
>         )
>
>  /* enums need to be exported to user space */
> --
> 2.39.2
>


-- 
Julian Sun <sunjunchao2870@gmail.com>

  reply	other threads:[~2024-08-20  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  9:49 [PATCH] writeback: Refine the show_inode_state() macro definition Julian Sun
2024-08-20  9:54 ` Julian Sun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-20  9:52 Julian Sun
2024-08-27 16:21 ` Jan Kara
2024-08-28  7:44   ` 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=CAHB1NagnXCDh_dVMX7TLBamtyF+G_1Ug0vohQg+jkJs8e2RuGg@mail.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).