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 v1 0/3] Optimize host lock on TR send/compl paths and utilize UTRLCNR
Date: Mon, 24 May 2021 01:36:55 -0700 [thread overview]
Message-ID: <1621845419-14194-1-git-send-email-cang@codeaurora.org> (raw)
By optimizing host lock usage on TR send/compl paths and utilizing UTRLCNR,
we can get considerable gain in both random read and random write performance.
Can Guo (3):
scsi: ufs: Remove a redundant command completion logic in error
handler
scsi: ufs: Optimize host lock on transfer requests send/compl paths
scsi: ufs: Utilize Transfer Request List Completion Notification
Register
drivers/scsi/ufs/ufshcd.c | 309 +++++++++++++++++++++++-----------------------
drivers/scsi/ufs/ufshcd.h | 7 +-
drivers/scsi/ufs/ufshci.h | 1 +
3 files changed, 162 insertions(+), 155 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2021-05-24 8:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 8:36 Can Guo [this message]
2021-05-24 8:36 ` [PATCH v1 1/3] scsi: ufs: Remove a redundant command completion logic in error handler Can Guo
2021-05-24 16:43 ` Bart Van Assche
2021-05-25 4:15 ` Stanley Chu
2021-05-31 7:14 ` Bean Huo
2021-05-24 8:36 ` [PATCH v1 2/3] scsi: ufs: Optimize host lock on transfer requests send/compl paths Can Guo
2021-05-24 11:25 ` kernel test robot
2021-06-08 17:53 ` Nathan Chancellor
2021-06-09 1:01 ` Can Guo
2021-05-24 20:10 ` Bart Van Assche
2021-05-25 1:34 ` Asutosh Das (asd)
2021-05-25 8:24 ` Avri Altman
2021-05-28 7:30 ` Avri Altman
2021-06-02 21:18 ` Asutosh Das (asd)
2021-05-25 1:40 ` Can Guo
2021-05-25 16:40 ` Bart Van Assche
2021-05-31 16:04 ` Bean Huo
2021-06-02 2:14 ` Can Guo
2021-06-03 0:18 ` Bart Van Assche
2021-06-03 2:54 ` Stanley Chu
2021-06-04 1:49 ` Can Guo
2021-06-17 2:49 ` Bart Van Assche
2021-06-23 2:04 ` Can Guo
2021-06-28 22:58 ` Bart Van Assche
2021-06-29 5:41 ` Can Guo
2021-07-01 15:57 ` Bart Van Assche
2021-05-24 8:36 ` [PATCH v1 3/3] scsi: ufs: Utilize Transfer Request List Completion Notification Register Can Guo
2021-05-31 16:05 ` Bean Huo
2021-06-03 2:54 ` Stanley Chu
2021-06-16 3:48 ` [PATCH v1 0/3] Optimize host lock on TR send/compl paths and utilize UTRLCNR 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=1621845419-14194-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;
as well as URLs for NNTP newsgroup(s).