From: Can Guo <cang@codeaurora.org>
To: Greg KH <greg@kroah.com>
Cc: asutoshd@codeaurora.org, nguyenb@codeaurora.org,
hongwus@codeaurora.org, rnayak@codeaurora.org,
linux-scsi@vger.kernel.org, kernel-team@android.com,
saravanak@google.com, salyzyn@google.com,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] scsi: ufs-qcom: Add one sysfs node to monitor performance
Date: Wed, 06 Jan 2021 08:51:42 +0800 [thread overview]
Message-ID: <684aabf8070279e380e03ec7b891330d@codeaurora.org> (raw)
In-Reply-To: <X/Q+/MSk1d2SW3lA@kroah.com>
On 2021-01-05 18:27, Greg KH wrote:
> Oops, forgot the big problem that I noticed:
>
> On Mon, Jan 04, 2021 at 07:15:51PM -0800, Can Guo wrote:
>> +static ssize_t monitor_show(struct device *dev, struct
>> device_attribute *attr,
>> + char *buf)
>> +{
>> + struct ufs_hba *hba = dev_get_drvdata(dev);
>> + struct ufs_qcom_host *host = ufshcd_get_variant(hba);
>> + struct ufs_qcom_perf_monitor *mon = &host->monitor;
>> + unsigned long nr_sec_rd, nr_sec_wr, busy_us_rd, busy_us_wr;
>> + unsigned long lat_max_rd, lat_min_rd, lat_sum_rd, lat_avg_rd,
>> nr_req_rd;
>> + unsigned long lat_max_wr, lat_min_wr, lat_sum_wr, lat_avg_wr,
>> nr_req_wr;
>> + bool is_enabled;
>> +
>> + /*
>> + * Don't lock the host lock since user needs to cat the entry very
>> + * frequently during performance test, otherwise it may impact the
>> + * performance.
>> + */
>> + is_enabled = mon->enabled;
>> + if (!is_enabled)
>> + goto print_usage;
>> +
>> + nr_sec_rd = mon->nr_sec_rw[READ];
>> + nr_sec_wr = mon->nr_sec_rw[WRITE];
>> + busy_us_rd = ktime_to_us(mon->total_busy[READ]);
>> + busy_us_wr = ktime_to_us(mon->total_busy[WRITE]);
>> +
>> + nr_req_rd = mon->nr_req[READ];
>> + lat_max_rd = ktime_to_us(mon->lat_max[READ]);
>> + lat_min_rd = ktime_to_us(mon->lat_min[READ]);
>> + lat_sum_rd = ktime_to_us(mon->lat_sum[READ]);
>> + lat_avg_rd = lat_sum_rd / nr_req_rd;
>> +
>> + nr_req_wr = mon->nr_req[WRITE];
>> + lat_max_wr = ktime_to_us(mon->lat_max[WRITE]);
>> + lat_min_wr = ktime_to_us(mon->lat_min[WRITE]);
>> + lat_sum_wr = ktime_to_us(mon->lat_sum[WRITE]);
>> + lat_avg_wr = lat_sum_wr / nr_req_wr;
>> +
>> + return scnprintf(buf, PAGE_SIZE, "Read %lu %s %lu us, %lu %s max %lu
>> | min %lu | avg %lu | sum %lu\nWrite %lu %s %lu us, %lu %s max %lu |
>> min %lu | avg %lu | sum %lu\n",
>> + nr_sec_rd, "sectors (in 512 bytes) in ", busy_us_rd,
>> + nr_req_rd, "read reqs completed, latencies in us: ",
>> + lat_max_rd, lat_min_rd, lat_avg_rd, lat_sum_rd,
>> + nr_sec_wr, "sectors (in 512 bytes) in ", busy_us_wr,
>> + nr_req_wr, "write reqs completed, latencies in us: ",
>> + lat_max_wr, lat_min_wr, lat_avg_wr, lat_sum_wr);
>
> sysfs is one-value-per-file, not
> throw-everything-in-one-file-and-hope-userspace-can-parse-it.
>
> This is not acceptable at all. Why not just use debugfs for stats like
> this?
>
> Also, use sysfs_emit() for any new sysfs files please.
>
> thanks,
>
> greg k-h
Hi Greg,
Thanks for the comments, I will rework the change to make it right.
Regards,
Can Guo.
prev parent reply other threads:[~2021-01-06 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 3:15 [PATCH v1 0/2] Introduce a vops to get info of command completion Can Guo
2021-01-05 3:15 ` [PATCH 1/2] scsi: ufs: " Can Guo
2021-01-05 3:15 ` [PATCH 2/2] scsi: ufs-qcom: Add one sysfs node to monitor performance Can Guo
2021-01-05 10:25 ` Greg KH
2021-01-05 10:27 ` Greg KH
2021-01-06 0:51 ` Can Guo [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=684aabf8070279e380e03ec7b891330d@codeaurora.org \
--to=cang@codeaurora.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=greg@kroah.com \
--cc=hongwus@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nguyenb@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=salyzyn@google.com \
--cc=saravanak@google.com \
/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