[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <43b022e5-18ba-4f03-907b-4bf148fa102c@nvidia.com>
Date: Tue, 18 Jun 2024 00:28:57 +0000
From: Chaitanya Kulkarni <chaitanyak@...dia.com>
To: Dongliang Cui <dongliang.cui@...soc.com>, "axboe@...nel.dk"
<axboe@...nel.dk>, "rostedt@...dmis.org" <rostedt@...dmis.org>,
"mhiramat@...nel.org" <mhiramat@...nel.org>, "mathieu.desnoyers@...icios.com"
<mathieu.desnoyers@...icios.com>, "ebiggers@...nel.org"
<ebiggers@...nel.org>, "bvanassche@....org" <bvanassche@....org>
CC: "ke.wang@...soc.com" <ke.wang@...soc.com>, "hongyu.jin.cn@...il.com"
<hongyu.jin.cn@...il.com>, "niuzhiguo84@...il.com" <niuzhiguo84@...il.com>,
"hao_hao.wang@...soc.com" <hao_hao.wang@...soc.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"akailash@...gle.com" <akailash@...gle.com>, "cuidongliang390@...il.com"
<cuidongliang390@...il.com>
Subject: Re: [PATCH v5] block: Add ioprio to block_rq tracepoint
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@...soc.com>
Looks useful to me.
Reviewed-by: Chaitanya Kulkarni <kch@...dia.com>
-ck
Powered by blists - more mailing lists