From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: <peter.wang@mediatek.com>
Cc: <linux-scsi@vger.kernel.org>, <martin.petersen@oracle.com>,
<avri.altman@sandisk.com>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>, <wsd_upstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>, <chun-hung.wu@mediatek.com>,
<alice.chao@mediatek.com>, <cc.chou@mediatek.com>,
<chaotian.jing@mediatek.com>, <tun-yu.yu@mediatek.com>,
<eddie.huang@mediatek.com>, <naomi.chu@mediatek.com>,
<ed.tsai@mediatek.com>, <bvanassche@acm.org>
Subject: Re: [PATCH v2] ufs: core: Avoid IRQ thread wakeup during active UIC command
Date: Sat, 07 Mar 2026 11:07:21 -0500 [thread overview]
Message-ID: <yq1ldg3wrmc.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260306054419.3816557-1-peter.wang@mediatek.com> (peter wang's message of "Fri, 6 Mar 2026 13:43:02 +0800")
Peter,
> Only return IRQ_WAKE_THREAD when MCQ and ESI are not enabled and no
> UIC command is active. The default UIC command timeout is 500ms, Using
> threaded IRQs during an active UIC command increases the risk of
> timeout due to possible preemption by other system IRQs.
Applied to 7.1/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2026-03-07 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260317171131eucas1p25dd55bf1aad6d5b310526d51885b3b7a@eucas1p2.samsung.com>
2026-03-06 5:43 ` [PATCH v2] ufs: core: Avoid IRQ thread wakeup during active UIC command peter.wang
2026-03-06 16:34 ` Bart Van Assche
2026-03-07 16:07 ` Martin K. Petersen [this message]
2026-03-16 1:41 ` Martin K. Petersen
2026-03-17 17:11 ` Marek Szyprowski
2026-03-18 6:57 ` Peter Wang (王信友)
2026-03-18 8:14 ` Marek Szyprowski
2026-03-19 12:39 ` Peter Wang (王信友)
2026-03-19 20:30 ` Bart Van Assche
2026-03-20 2:09 ` Peter Wang (王信友)
2026-03-18 15:50 ` Bart Van Assche
2026-03-18 17:13 ` Marek Szyprowski
2026-03-18 17:32 ` Bart Van Assche
2026-03-18 19:32 ` Marek Szyprowski
2026-03-18 20:38 ` Bart Van Assche
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=yq1ldg3wrmc.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@sandisk.com \
--cc=bvanassche@acm.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=ed.tsai@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=tun-yu.yu@mediatek.com \
--cc=wsd_upstream@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