Linux Trace Kernel
 help / color / mirror / Atom feed
From: liubaolin <liubaolin12138@163.com>
To: almaz.alexandrovich@paragon-software.com, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com
Cc: linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
	linux-trace-kernel@vger.kernel.org, liubaolin12138@gmail.com,
	Baolin Liu <liubaolin@kylinos.cn>,
	liubaolin12138@163.com
Subject: Re: [PATCH v3 v3 0/7] ntfs3: add tracepoints for core filesystem paths
Date: Fri, 7 Aug 2026 09:07:38 +0800	[thread overview]
Message-ID: <7800d0c3-e405-429f-8b3e-a7e7aa372085@163.com> (raw)
In-Reply-To: <20260807010354.2277156-1-liubaolin12138@163.com>


Dear Steve,

    I have reordered the tracepoint fields across the series as 
suggested to reduce padding on 64-bit systems. These changes are 
included in v3.
    Looking forward to your review and feedback.

Thanks,
Baolin

在 2026/8/7 09:03, Baolin Liu 写道:
> From: Baolin Liu <liubaolin@kylinos.cn>
> 
> This series adds an initial set of tracepoints for ntfs3 core paths.
> 
> The tracepoints cover:
>     - mount and log replay
>     - namei operations
>     - directory index operations
>     - allocation and block mapping
>     - iomap operations
>     - file I/O entry points
> 
> Changes in v3:
>     - Reorder tracepoint fields across the series to reduce padding on
>       64-bit systems
> 
> Baolin Liu (7):
>    ntfs3: add mount and log replay tracepoints
>    ntfs3: add namei tracepoints
>    ntfs3: add create inode tracepoint
>    ntfs3: add directory index tracepoints
>    ntfs3: add allocation tracepoints
>    ntfs3: add iomap tracepoints
>    ntfs3: add file I/O tracepoints
> 
>   MAINTAINERS                  |   1 +
>   fs/ntfs3/attrib.c            |   9 +
>   fs/ntfs3/dir.c               |   3 +
>   fs/ntfs3/file.c              |   5 +
>   fs/ntfs3/fslog.c             |   3 +
>   fs/ntfs3/index.c             |   8 +
>   fs/ntfs3/inode.c             |   7 +
>   fs/ntfs3/namei.c             |   5 +
>   fs/ntfs3/super.c             |  11 +-
>   include/trace/events/ntfs3.h | 389 +++++++++++++++++++++++++++++++++++
>   10 files changed, 440 insertions(+), 1 deletion(-)
>   create mode 100644 include/trace/events/ntfs3.h
> 


      parent reply	other threads:[~2026-08-07  1:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  1:03 [PATCH v3 v3 0/7] ntfs3: add tracepoints for core filesystem paths Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 1/7] ntfs3: add mount and log replay tracepoints Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 2/7] ntfs3: add namei tracepoints Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 3/7] ntfs3: add create inode tracepoint Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 4/7] ntfs3: add directory index tracepoints Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 5/7] ntfs3: add allocation tracepoints Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 6/7] ntfs3: add iomap tracepoints Baolin Liu
2026-08-07  1:03 ` [PATCH v3 v3 7/7] ntfs3: add file I/O tracepoints Baolin Liu
2026-08-07  1:07 ` liubaolin [this message]

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=7800d0c3-e405-429f-8b3e-a7e7aa372085@163.com \
    --to=liubaolin12138@163.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=liubaolin12138@gmail.com \
    --cc=liubaolin@kylinos.cn \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox