From: Can Guo <cang@codeaurora.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, linux-scsi@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v2 0/2] Introduce hba performance monitoring sysfs nodes
Date: Wed, 31 Mar 2021 11:52:44 +0800 [thread overview]
Message-ID: <6aeb31ca744b1232808bddb7397edf4f@codeaurora.org> (raw)
In-Reply-To: <ce9a2333-437e-143a-a0f0-c5f532a2c423@acm.org>
On 2021-03-31 11:34, Bart Van Assche wrote:
> On 3/30/21 8:14 PM, Can Guo wrote:
>> It works like:
>> /sys/bus/platform/drivers/ufshcd/*/monitor # echo 4096 >
>> monitor_chunk_size
>> /sys/bus/platform/drivers/ufshcd/*/monitor # echo 1 > monitor_enable
>> /sys/bus/platform/drivers/ufshcd/*/monitor # grep ^ /dev/null *
>> monitor_chunk_size:4096
>> monitor_enable:1
>> read_nr_requests:17
>> read_req_latency_avg:169
>> read_req_latency_max:594
>> read_req_latency_min:66
>> read_req_latency_sum:2887
>> read_total_busy:2639
>> read_total_sectors:136
>> write_nr_requests:116
>> write_req_latency_avg:440
>> write_req_latency_max:4921
>> write_req_latency_min:23
>> write_req_latency_sum:51052
>> write_total_busy:19584
>> write_total_sectors:928
>
> Are any of these attributes UFS-specific? If not, isn't this
> functionality that should be added to the block layer instead of to the
> UFS driver?
>
Hi Bart,
I didn't think that before because we've already have the powerful
"blktrace"
tool to collect the overall statistics of each layer.
I add this because I find it really come handy when
debug/analyze/profile
UFS driver/HW performance. And there will be UFS-specific nodes to be
added later to monitor statistics like UFS scaling, gating, doorbell,
write
booster, HPB and etc.
Thanks.
Can Guo.
> Thanks,
>
> Bart.
next prev parent reply other threads:[~2021-03-31 3:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 3:14 [PATCH v2 0/2] Introduce hba performance monitoring sysfs nodes Can Guo
2021-03-31 3:14 ` [PATCH v2 1/2] scsi: ufs: Introduce hba performance monitor " Can Guo
2021-03-31 10:19 ` kernel test robot
2021-03-31 12:05 ` kernel test robot
2021-03-31 3:14 ` [PATCH v2 2/2] scsi: ufs: Add support for hba performance monitor Can Guo
2021-03-31 3:34 ` [PATCH v2 0/2] Introduce hba performance monitoring sysfs nodes Bart Van Assche
2021-03-31 3:52 ` Can Guo [this message]
2021-03-31 6:35 ` Avri Altman
2021-03-31 7:44 ` Can Guo
2021-03-31 8:18 ` Avri Altman
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=6aeb31ca744b1232808bddb7397edf4f@codeaurora.org \
--to=cang@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--cc=bvanassche@acm.org \
--cc=hongwus@codeaurora.org \
--cc=kernel-team@android.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nguyenb@codeaurora.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