From: Bean Huo <beanhuo@iokpp.de>
To: hyenc.jeong@samsung.com,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"mkp@kernel.org" <mkp@kernel.org>,
"avri.altman@sandisk.com" <avri.altman@sandisk.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: Jinyoung Choi <j-young.choi@samsung.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"can.guo@oss.qualcomm.com" <can.guo@oss.qualcomm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] scsi: ufs: batch device-init reads with UFS 5.0 aggregated read
Date: Fri, 02 Oct 2026 11:24:15 +0200 [thread overview]
Message-ID: <8ab9b08e12bf60e89a60a86137a23e9164e43839.camel@iokpp.de> (raw)
In-Reply-To: <1860250540.01790747102385.JavaMail.epsvc@epcpadp1new>
On Wed, 2026-09-30 at 14:02 +0900, Hyeoncheol Jeong wrote:
> No functional change for pre-5.0 devices.
>
> Motivation: on a Qualcomm SM8850 platform with a Samsung UFS 5.0 device,
> timing raw UPIU queries over BSG (100 iterations) shows that replacing the
> device-init read burst with a single aggregated read reduces the query
> time by 75-78% (min 75.3%, avg 76.4%, max 78.5%).
Hi Jeong,
I don't know if you have plan to enable this feature in UEFI or any bootloaders
to eliminate the boot overhead becaused of query iterations.
Kind regards,
Bean
next prev parent reply other threads:[~2026-10-02 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260930050201epcms2p13ab67182445b0555acc8d27b927cda86@epcms2p1>
2026-09-30 5:02 ` Hyeoncheol Jeong
2026-10-02 9:24 ` Bean Huo [this message]
[not found] ` <CGME20260930050201epcms2p13ab67182445b0555acc8d27b927cda86@epcms2p8>
2026-10-06 7:17 ` Hyeoncheol Jeong
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=8ab9b08e12bf60e89a60a86137a23e9164e43839.camel@iokpp.de \
--to=beanhuo@iokpp.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=can.guo@oss.qualcomm.com \
--cc=hyenc.jeong@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=peter.wang@mediatek.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
all inboxes | Powered by JetHome®