mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Huan Tang <tanghuan@vivo.com>, peter.wang@mediatek.com
Cc: James.Bottomley@HansenPartnership.com, alim.akhtar@samsung.com,
	avri.altman@wdc.com, ebiggers@google.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	manivannan.sadhasivam@linaro.org, martin.petersen@oracle.com,
	minwoo.im@samsung.com, opensource.kernel@vivo.com,
	quic_nguyenb@quicinc.com
Subject: Re: [PATCH] ufs: core: add caps UFSHCD_CAP_MCQ_EN
Date: Mon, 21 Apr 2025 23:57:23 -0700	[thread overview]
Message-ID: <d78b244b-e032-4d6f-b6bf-87be2a98693d@acm.org> (raw)
In-Reply-To: <20250422062555.694-1-tanghuan@vivo.com>


On 4/21/25 11:25 PM, Huan Tang wrote:
> I found that using low-end UFS in SoCs that support MCQ may cause
> device latency to reach extreme values.

Hi Huan,

What is the root-cause of the high latency? If it is the time spent in
UFS interrupt handlers, please try to switch to threaded interrupt
handlers instead of disabling MCQ. See also
https://lore.kernel.org/linux-scsi/20250407-topic-ufs-use-threaded-irq-v3-0-08bee980f71e@linaro.org/

Bart.

  reply	other threads:[~2025-04-22  6:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 13:51 Huan Tang
2025-04-21 13:58 ` Huan Tang
2025-04-22  2:55 ` Peter Wang (王信友)
2025-04-22  6:25   ` Huan Tang
2025-04-22  6:57     ` Bart Van Assche [this message]
2025-04-22  7:22       ` Huan Tang
2025-04-22  6:57     ` Avri Altman
2025-04-22  7:04       ` Huan Tang
2025-04-22  7:06       ` Huan Tang
2025-04-22  8:11         ` Avri Altman
2025-04-22  7:51     ` Peter Wang (王信友)

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=d78b244b-e032-4d6f-b6bf-87be2a98693d@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=ebiggers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=minwoo.im@samsung.com \
    --cc=opensource.kernel@vivo.com \
    --cc=peter.wang@mediatek.com \
    --cc=quic_nguyenb@quicinc.com \
    --cc=tanghuan@vivo.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®