From: Bart Van Assche <bvanassche@acm.org>
To: Yihang Li <liyihang9@h-partners.com>,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, liyihang9@huawei.com,
liuyonglong@huawei.com, prime.zeng@hisilicon.com
Subject: Re: [PATCH 0/4] scsi: hisi_sas: Switch to use tasklet over threaded irq handling
Date: Fri, 22 Aug 2025 08:17:35 -0700 [thread overview]
Message-ID: <f02e9bb8-3477-4fa7-8b20-72bd518407ed@acm.org> (raw)
In-Reply-To: <20250822075951.2051639-1-liyihang9@h-partners.com>
On 8/22/25 12:59 AM, Yihang Li wrote:
> We found that when the CPU handling the interrupt thread is occupied by
> other high-priority processes, the interrupt thread will not be scheduled.
> So there is a change to switch the driver to use tasklet over threaded
> interrupt handling.
Tasklets have severe disadvantages and hence their removal has been
proposed several times. See e.g. https://lwn.net/Articles/960041/.
There must be a better solution than switching to tasklets.
Bart.
next prev parent reply other threads:[~2025-08-22 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:59 Yihang Li
2025-08-22 7:59 ` [PATCH 1/4] scsi: hisi_sas: Use tasklet to process CQ interrupts Yihang Li
2025-08-22 7:59 ` [PATCH 2/4] scsi: hisi_sas: replace spin_lock/spin_unlock with spin_lock_irqsave/spin_unlock_restore Yihang Li
2025-08-22 7:59 ` [PATCH 3/4] scsi: hisi_sas: Remove cond_resched() in bottom half of interrupt Yihang Li
2025-08-22 7:59 ` [PATCH 4/4] scsi: hisi_sas: Remove unused hisi_sas_sync_poll_cqs() Yihang Li
2025-08-22 15:17 ` Bart Van Assche [this message]
2025-08-25 1:42 ` [PATCH 0/4] scsi: hisi_sas: Switch to use tasklet over threaded irq handling Yihang Li
2025-08-25 16:12 ` Bart Van Assche
2025-08-27 2:11 ` Yihang Li
2025-08-27 3:18 ` Bart Van Assche
2025-08-26 8:47 ` Jason Yan
2025-08-26 13:45 ` Bart Van Assche
2025-08-27 2:14 ` Yihang Li
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=f02e9bb8-3477-4fa7-8b20-72bd518407ed@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=liyihang9@h-partners.com \
--cc=liyihang9@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=prime.zeng@hisilicon.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®