mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "孙魁 (Kui Sun)" <kui.sun@unisoc.com>,
	"Neil Armstrong" <neil.armstrong@linaro.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>,
	"andre.draszik@linaro.org" <andre.draszik@linaro.org>
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>,
	"André Draszik" <andre.draszik@linaro.org>
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 07:56:23 -0700	[thread overview]
Message-ID: <d426b4d5-cdf5-4090-8e94-62e652f712dc@acm.org> (raw)
In-Reply-To: <12a8417dc8644a71b9cb25c53c93805a@zeshmbx08.spreadtrum.com>

On 7/10/26 12:17 AM, 孙魁 (Kui Sun) wrote:
> Through investigation, we identified that upstream commit
> 3c7ac40d732232fec0ba31d0a5e3cc9c112fc2e7, merged in April 2025, is
> likely responsible for this performance drop.
Two fixes for that commit are present in the upstream kernel. Are these
fixes present in your kernel tree?

commit eabcac808ca3ee9878223d4b49b750979029016b
Author: Bart Van Assche <bvanassche@acm.org>
Date:   Fri Aug 15 08:58:23 2025 -0700

     scsi: ufs: core: Fix IRQ lock inversion for the SCSI host lock

commit 034d319c8899e8c5c0a35c6692c7fc7e8c12c374
Author: Nitin Rawat <quic_nitirawa@quicinc.com>
Date:   Tue Jul 29 04:27:11 2025 +0530

     scsi: ufs: core: Fix interrupt handling for MCQ Mode

Thanks,

Bart.

  parent reply	other threads:[~2026-07-10 14:56 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
2026-07-10 14:56 ` Bart Van Assche [this message]
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=d426b4d5-cdf5-4090-8e94-62e652f712dc@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Rain.Zhang@unisoc.com \
    --cc=Wenchao.Chen@unisoc.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andre.draszik@linaro.org \
    --cc=avri.altman@wdc.com \
    --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