mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: chaitanyak@nvidia.com, dlemoal@kernel.org, hare@suse.de,
	hch@lst.de,  john.g.garry@oracle.com,
	linux-block@vger.kernel.org,  linux-btrace@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	 linux-trace-kernel@vger.kernel.org, martin.petersen@oracle.com,
	 mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
	naohiro.aota@wdc.com,  rostedt@goodmis.org,
	shinichiro.kawasaki@wdc.com
Subject: Re: [PATCH v5 00/16] block: add blktrace support for zoned block devies
Date: Wed, 22 Oct 2025 11:14:26 -0600	[thread overview]
Message-ID: <176115326663.119946.495631617143867642.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251022114115.213865-1-johannes.thumshirn@wdc.com>


On Wed, 22 Oct 2025 13:40:59 +0200, Johannes Thumshirn wrote:
> This patch series extends the kernel blktrace infrastructure to support
> tracing zoned block device commands. Zoned block devices (e.g., ZAC/ZBC and
> ZNS) introduce command types such as zone open, close, reset, finish, and zone
> append. These are currently not visible in blktrace, making it difficult to
> debug and analyze I/O workloads on zoned devices.
> 
> The patches in this series utilize the new trace points for these zone
> management operations, and propagate the necessary context to the blktrace
> logging path. These additions are designed to be backward-compatible, and are
> only active when zoned devices are in use.
> 
> [...]

Applied, thanks!

[01/16] blktrace: only calculate trace length once
        commit: a65988a0ad047dbdb8a1eb6f07540b980858b522
[02/16] blktrace: factor out recording a blktrace event
        commit: 472eca538358fc8a56884a8adb0cc6047bf05cf3
[03/16] blktrace: split out relaying a blktrace event
        commit: 04678e72e95f4165d58442b3ed108e06605984df
[04/16] blktrace: untangle if/else sequence in __blk_add_trace
        commit: 70e3c62b891281b94b9d449a381e033ce592acc8
[05/16] blktrace: change the internal action to 64bit
        commit: 370cd70a402f972f6d7a7e54ba5a82d1a72c762f
[06/16] blktrace: split do_blk_trace_setup into two functions
        commit: 42da88a724d8a3b92ade35ae2ef4d5e5a491df2d
[07/16] blktrace: add definitions for blk_user_trace_setup2
        commit: 0d8627cc936de8ea04f3cc1e6921c63fb72cc199
[08/16] blktrace: pass blk_user_trace2 to setup functions
        commit: 113cbd62824afdf62d2f3f092809cf37cc7f1dd8
[09/16] blktrace: add definitions for struct blk_io_trace2
        commit: c44347d606260f36a81f6d8415a5af33cb3015fa
[10/16] blktrace: differentiate between blk_io_trace versions
        commit: 915bb53860c3a6cc3dd2c9a5e0d1988ada0e377d
[11/16] blktrace: move trace_note to blk_io_trace2
        commit: 67bfa74d81bae9271f6ec72d2058d081732949cb
[12/16] blktrace: move ftrace blk_io_tracer to blk_io_trace2
        commit: 4d8bc7bd4f73c6b34ba29d3e8277864c6e0a44a7
[13/16] blktrace: add block trace commands for zone operations
        commit: f9ee38bbf70fb20584625849a253c8652176fa66
[14/16] blktrace: expose ZONE APPEND completions to blktrace
        commit: 1c164fcc1b08e75f1cad1532718f09cddc0ddebe
[15/16] blktrace: trace zone write plugging operations
        commit: 3f6722816a73e2017599d965683dbe71833afd7a
[16/16] blktrace: handle BLKTRACESETUP2 ioctl
        commit: 4ae8efb4f907383a16abf3c59b353763e31ae106

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2025-10-22 17:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 11:40 Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 01/16] blktrace: only calculate trace length once Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 02/16] blktrace: factor out recording a blktrace event Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 03/16] blktrace: split out relaying " Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 04/16] blktrace: untangle if/else sequence in __blk_add_trace Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 05/16] blktrace: change the internal action to 64bit Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 06/16] blktrace: split do_blk_trace_setup into two functions Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 07/16] blktrace: add definitions for blk_user_trace_setup2 Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 08/16] blktrace: pass blk_user_trace2 to setup functions Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 09/16] blktrace: add definitions for struct blk_io_trace2 Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 10/16] blktrace: differentiate between blk_io_trace versions Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 11/16] blktrace: move trace_note to blk_io_trace2 Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 12/16] blktrace: move ftrace blk_io_tracer " Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 13/16] blktrace: add block trace commands for zone operations Johannes Thumshirn
2025-10-22 12:31   ` Damien Le Moal
2025-10-22 11:41 ` [PATCH v5 14/16] blktrace: expose ZONE APPEND completions to blktrace Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 15/16] blktrace: trace zone write plugging operations Johannes Thumshirn
2025-10-22 11:41 ` [PATCH v5 16/16] blktrace: handle BLKTRACESETUP2 ioctl Johannes Thumshirn
2025-10-22 17:14 ` Jens Axboe [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=176115326663.119946.495631617143867642.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrace@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=naohiro.aota@wdc.com \
    --cc=rostedt@goodmis.org \
    --cc=shinichiro.kawasaki@wdc.com \
    /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

all inboxes | Powered by JetHome®