From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"quic_mnaresh@quicinc.com" <quic_mnaresh@quicinc.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"chu.stanley@gmail.com" <chu.stanley@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"quic_cang@quicinc.com" <quic_cang@quicinc.com>
Subject: Re: [PATCH V5 1/2] ufs: core: Add CPU latency QoS support for ufs driver
Date: Fri, 15 Dec 2023 06:58:52 +0000 [thread overview]
Message-ID: <c00aeb47c67599d632cced1017696cf1295d83ea.camel@mediatek.com> (raw)
In-Reply-To: <20231213124353.16407-2-quic_mnaresh@quicinc.com>
On Wed, 2023-12-13 at 18:13 +0530, Maramaina Naresh wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> Register ufs driver to CPU latency PM QoS framework to improve
> ufs device random io performance.
>
> PM QoS initialization will insert new QoS request into the CPU
> latency QoS list with the maximum latency PM_QOS_DEFAULT_VALUE
> value.
>
> UFS driver will vote for performance mode on scale up and power
> save mode for scale down.
>
> If clock scaling feature is not enabled then voting will be based
> on clock on or off condition.
>
> Provided sysfs interface to enable/disable PM QoS feature.
>
> tiotest benchmark tool io performance results on sm8550 platform:
>
> 1. Without PM QoS support
> Type (Speed in) | Average of 18 iterations
> Random Write(IPOS) | 41065.13
> Random Read(IPOS) | 37101.3
>
> 2. With PM QoS support
> Type (Speed in) | Average of 18 iterations
> Random Write(IPOS) | 46784.9
> Random Read(IPOS) | 42943.4
> (Improvement with PM QoS = ~15%).
>
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
next prev parent reply other threads:[~2023-12-15 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 12:43 [PATCH V5 0/2] Add CPU latency QoS support for ufs driver Maramaina Naresh
2023-12-13 12:43 ` [PATCH V5 1/2] ufs: core: " Maramaina Naresh
2023-12-15 6:58 ` Peter Wang (王信友) [this message]
2023-12-18 21:55 ` Bart Van Assche
2023-12-13 12:43 ` [PATCH V5 2/2] ufs: ufs-mediatek: Migrate to UFSHCD generic CPU latency PM QoS support Maramaina Naresh
2023-12-15 6:59 ` Peter Wang (王信友)
2023-12-15 9:05 ` [PATCH V5 0/2] Add CPU latency QoS support for ufs driver Avri Altman
2023-12-17 17:03 ` Naresh Maramaina
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=c00aeb47c67599d632cced1017696cf1295d83ea.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=chu.stanley@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=quic_cang@quicinc.com \
--cc=quic_mnaresh@quicinc.com \
--cc=quic_nguyenb@quicinc.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