mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: rostedt@goodmis.org, mhiramat@kernel.org,
	 mathieu.desnoyers@efficios.com, ebiggers@kernel.org,
	bvanassche@acm.org,  Dongliang Cui <dongliang.cui@unisoc.com>
Cc: ke.wang@unisoc.com, hongyu.jin.cn@gmail.com,
	niuzhiguo84@gmail.com,  hao_hao.wang@unisoc.com,
	linux-block@vger.kernel.org,  linux-kernel@vger.kernel.org,
	akailash@google.com,  cuidongliang390@gmail.com
Subject: Re: [PATCH v5] block: Add ioprio to block_rq tracepoint
Date: Fri, 28 Jun 2024 10:36:35 -0600	[thread overview]
Message-ID: <171959259559.887658.11944465958863897006.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240614074936.113659-1-dongliang.cui@unisoc.com>


On Fri, 14 Jun 2024 15:49:36 +0800, 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]
> 
> [...]

Applied, thanks!

[1/1] block: Add ioprio to block_rq tracepoint
      commit: aa6ff4eb7c10d9a6532db3ea9e78124bf14e70ae

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2024-06-28 16:36 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
2024-06-28  6:38   ` dongliang cui
2024-06-28 16:36 ` 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=171959259559.887658.11944465958863897006.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akailash@google.com \
    --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®