From: Can Guo <cang@codeaurora.org>
To: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, linux-scsi@vger.kernel.org,
kernel-team@android.com, cang@codeaurora.org
Subject: [PATCH v5 0/2] Introduce hba performance monitoring sysfs nodes
Date: Wed, 21 Apr 2021 19:28:38 -0700 [thread overview]
Message-ID: <1619058521-35307-1-git-send-email-cang@codeaurora.org> (raw)
Add a new sysfs group which has nodes to monitor data/request transfer
performance. This sysfs group has nodes showing total sectors/requests
transferred, total busy time spent and max/min/avg/sum latencies. This
group can be enhanced later to show more UFS driver layer performance
data during runtime.
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
Change since v4:
- Use lrbp->compl_time_stamp as now in ufshcd_update_monitor()
Change since v3:
- Rebased
Change since v2:
- Fixed a sparse error
Change since v1:
- Moved code from ufs-qcom.c to ufshcd.c
Can Guo (2):
scsi: ufs: Introduce hba performance monitor sysfs nodes
scsi: ufs: Add support for hba performance monitor
Documentation/ABI/testing/sysfs-driver-ufs | 126 +++++++++++++++
drivers/scsi/ufs/ufs-sysfs.c | 237 +++++++++++++++++++++++++++++
drivers/scsi/ufs/ufshcd.c | 62 ++++++++
drivers/scsi/ufs/ufshcd.h | 21 +++
4 files changed, 446 insertions(+)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2021-04-22 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210422022910epcas2p1c28bc11ee4118559d967e83bd8434c7f@epcms2p5>
2021-04-22 2:28 ` Can Guo [this message]
2021-04-22 2:28 ` [PATCH v5 1/2] scsi: ufs: Introduce hba performance monitor sysfs nodes Can Guo
2021-05-12 20:21 ` Bean Huo
2021-05-13 1:15 ` Can Guo
2021-05-13 21:10 ` Bean Huo
2021-04-22 2:28 ` [PATCH v5 2/2] scsi: ufs: Add support for hba performance monitor Can Guo
2021-05-13 21:11 ` Bean Huo
2021-05-06 5:00 ` [PATCH v5 0/2] Introduce hba performance monitoring sysfs nodes Daejun Park
2021-05-15 2:56 ` Martin K. Petersen
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=1619058521-35307-1-git-send-email-cang@codeaurora.org \
--to=cang@codeaurora.org \
--cc=asutoshd@codeaurora.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