From: "André Draszik" <andre.draszik@linaro.org>
To: "孙魁 (Kui Sun)" <kui.sun@unisoc.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Bart Van Assche" <bvanassche@acm.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Avri Altman" <avri.altman@wdc.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"\"Martin K. Petersen\"" <martin.petersen@oracle.com>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Will McVicker" <willmcvicker@google.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"kernel-team@android.com" <kernel-team@android.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"张如泉 (Rain Zhang)" <Rain.Zhang@unisoc.com>,
"cixi.geng@linux.dev" <cixi.geng@linux.dev>,
"唐月林 (Yuelin Tang)" <yuelin.tang@unisoc.com>,
"陈文超 (Wenchao Chen)" <Wenchao.Chen@unisoc.com>
Subject: Re: [RFC] Significant Random I/O Performance Regression in Linux Kernel 6.18 (Up to 27.7%) Likely Caused by Commit 3c7ac40d7322
Date: Fri, 10 Jul 2026 10:54:19 +0100 [thread overview]
Message-ID: <a4003ac352f382fa4ff329acdfa561eb06e77289.camel@linaro.org> (raw)
In-Reply-To: <12a8417dc8644a71b9cb25c53c93805a@zeshmbx08.spreadtrum.com>
Hi,
On Fri, 2026-07-10 at 07:17 +0000, 孙魁 (Kui Sun) wrote:
> Dear Kernel Maintainers,
>
> During our upgrade from Linux kernel 5.15 to Linux kernel 6.18, we observed a significant performance regression in random I/O
> workloads—with a maximum degradation of 27.7%.
[...]
> This issue is particularly pronounced in single-threaded, small-block I/O scenarios。
>
> To illustrate the impact, we conducted benchmark tests using AnTuTu on Unisoc T615 devices.
> The results are summarized below:
[...]
> Root Cause Identification
>
> Through investigation, we identified that upstream commit 3c7ac40d732232fec0ba31d0a5e3cc9c112fc2e7, merged in April 2025, is likely
> responsible for this performance drop.
> After locally reverting this commit on kernel 6.18, performance fully recovered:
>
> Table 4:Mixed Random Read/Write Speed Scores(After Revert)
> Device Kernel Version Test1 Test2 Test3 Average
> T615 5.15 18604 18314 17732 18216.67
> T615 6.18 13372 13081 13081 13178.00(↓27.66%)
> T615 6.18(reverted 3c7ac40) 18314 18604 18604 18507.33
>
Thank you for your above analysis. Your numbers match up well with my own
observations at the time in
https://lore.kernel.org/all/88d31a258feb36425ad73d0323077972f85f8341.camel@linaro.org/
[...]
> Request and Recommendations
>
> Given the tangible impact on mobile user experience, we kindly request the community to:
> 1. Consider reverting commit 3c7ac40d732232fec0ba31d0a5e3cc9c112fc2e7, or
> 2. Re-evaluate the proposed change in light of its effect on low-concurrency I/O paths, as discussed here:
> https://lore.kernel.org/lkml/88d31a258feb36425ad73d0323077972f85f8341.camel@linaro.org/
While originally I was trying to find a solution that doesn't regress existing
platforms and still works for the newly added platform, I can only second the request
for revert, given how important UFS is for mobile.
Mani was also in favour of reverting:
https://lore.kernel.org/all/4enen7mopxtx4ijl5qyrd2gnxvv3kygtlnhxpr64egckpvkja4@hjli25ndhxwc/
Cheers,
Andre'
next prev parent reply other threads:[~2026-07-10 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:17 孙魁 (Kui Sun)
2026-07-10 9:54 ` André Draszik [this message]
2026-07-10 14:56 ` Bart Van Assche
2026-07-11 11:21 ` 答复: " 孙魁 (Kui Sun)
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=a4003ac352f382fa4ff329acdfa561eb06e77289.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Rain.Zhang@unisoc.com \
--cc=Wenchao.Chen@unisoc.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=cixi.geng@linux.dev \
--cc=kernel-team@android.com \
--cc=kui.sun@unisoc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
--cc=peter.griffin@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.com \
--cc=yuelin.tang@unisoc.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®