mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, liuyonglong@huawei.com,
	prime.zeng@hisilicon.com
Subject: Re: [PATCH 0/4] scsi: hisi_sas: Switch to use tasklet over threaded irq handling
Date: Tue, 26 Aug 2025 20:18:29 -0700	[thread overview]
Message-ID: <bfdffd81-d844-4984-a8dd-ffad3e906f96@acm.org> (raw)
In-Reply-To: <f996d9cd-7be8-876e-680a-acf842afed5b@h-partners.com>

On 8/26/25 7:11 PM, Yihang Li wrote:
> In the interrupt thread context, the main tasks are handling abnormal I/O
> and calling.task_done()->scsi_done(). I believe these tasks are not
> suitable for execution in the interrupt context.

Most code that can be used in tasklet context is also safe to use in 
interrupt context. Does this patch series complete I/O requests from
tasklet context? Does that mean that it is also possible to complete
I/O requests from interrupt context? Or am I perhaps missing something?

Thanks,

Bart.

  reply	other threads:[~2025-08-27  3:18 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 ` [PATCH 0/4] scsi: hisi_sas: Switch to use tasklet over threaded irq handling Bart Van Assche
2025-08-25  1:42   ` 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 [this message]
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=bfdffd81-d844-4984-a8dd-ffad3e906f96@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=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®