From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"dlemoal@kernel.org" <dlemoal@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>
Subject: Re: [PATCH V2] blktrace: log dropped REQ_OP_ZONE_XXX events ver1
Date: Fri, 19 Dec 2025 23:50:36 +0000 [thread overview]
Message-ID: <3bbc39bf-b96d-4d68-8e32-bee5662c0653@nvidia.com> (raw)
In-Reply-To: <fc5f6ed4-5bd3-4c4d-82c3-cdab26dcbf94@wdc.com>
On 10/28/25 23:47, Johannes Thumshirn wrote:
> On 10/28/25 6:32 PM, Chaitanya Kulkarni wrote:
>> + if (version == 1 && IS_ENABLED(CONFIG_BLK_DEV_ZONED)) {
>> + pr_info("%s: blktrace events for REQ_OP_ZONE_XXX will be dropped\n",
>> + name);
>> + pr_info("use blktrace tools version >= 2 to track REQ_OP_ZONE_XXX\n");
> Jens hasn't merged the user-space part yet and I'm not sure he'll assign
> a dedicated version number for it. So I'd say hold this until he has.
>
Now Jen's has merged the userspace part, may I please get a reviewed-by if this
looks good?
-ck
next prev parent reply other threads:[~2025-12-19 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 17:32 [PATCH V2] blktrace: log dropped REQ_OP_ZONE_XXX events ver1 Chaitanya Kulkarni
2025-10-29 6:47 ` Johannes Thumshirn
2025-12-19 23:50 ` Chaitanya Kulkarni [this message]
2025-12-19 23:55 ` Damien Le Moal
2025-12-22 23:28 ` Jens Axboe
2025-12-23 2:13 ` Chaitanya Kulkarni
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=3bbc39bf-b96d-4d68-8e32-bee5662c0653@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=ckulkarnilinux@gmail.com \
--cc=dlemoal@kernel.org \
--cc=linux-block@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=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