From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Dongliang Cui <dongliang.cui@unisoc.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"ebiggers@kernel.org" <ebiggers@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>
Cc: "ke.wang@unisoc.com" <ke.wang@unisoc.com>,
"hongyu.jin.cn@gmail.com" <hongyu.jin.cn@gmail.com>,
"niuzhiguo84@gmail.com" <niuzhiguo84@gmail.com>,
"hao_hao.wang@unisoc.com" <hao_hao.wang@unisoc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akailash@google.com" <akailash@google.com>,
"cuidongliang390@gmail.com" <cuidongliang390@gmail.com>
Subject: Re: [PATCH v5] block: Add ioprio to block_rq tracepoint
Date: Tue, 18 Jun 2024 00:28:57 +0000 [thread overview]
Message-ID: <43b022e5-18ba-4f03-907b-4bf148fa102c@nvidia.com> (raw)
In-Reply-To: <20240614074936.113659-1-dongliang.cui@unisoc.com>
On 6/14/24 00:49, Dongliang Cui wrote:
> Sometimes we need to track the processing order of requests with
> ioprio set. So the ioprio of request can be useful information.
>
> Example：
>
> block_rq_insert: 8,0 RA 16384 () 6500840 + 32 be,0,6 [binder:815_3]
> block_rq_issue: 8,0 RA 16384 () 6500840 + 32 be,0,6 [binder:815_3]
> block_rq_complete: 8,0 RA () 6500840 + 32 be,0,6 [0]
>
> Signed-off-by: Dongliang Cui<dongliang.cui@unisoc.com>
Looks useful to me.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2024-06-18 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 7:49 Dongliang Cui
2024-06-14 16:40 ` Bart Van Assche
2024-06-17 7:59 ` dongliang cui
2024-06-17 17:02 ` Bart Van Assche
2024-06-17 17:07 ` Steven Rostedt
2024-06-17 21:30 ` Bart Van Assche
2024-06-18 0:28 ` Chaitanya Kulkarni [this message]
2024-06-28 6:38 ` dongliang cui
2024-06-28 16:36 ` Jens Axboe
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=43b022e5-18ba-4f03-907b-4bf148fa102c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=akailash@google.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=cuidongliang390@gmail.com \
--cc=dongliang.cui@unisoc.com \
--cc=ebiggers@kernel.org \
--cc=hao_hao.wang@unisoc.com \
--cc=hongyu.jin.cn@gmail.com \
--cc=ke.wang@unisoc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=niuzhiguo84@gmail.com \
--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
all inboxes | Powered by JetHome®