mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "André Draszik" <andre.draszik@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>,
	"Neil Armstrong" <neil.armstrong@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, linux-arm-msm@vger.kernel.org,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: core: move some irq handling back to hardirq (with time limit)
Date: Thu, 24 Jul 2025 09:02:54 -0700	[thread overview]
Message-ID: <2e7c2be8-dc58-4e18-9297-e8690565583b@acm.org> (raw)
In-Reply-To: <20250724-ufshcd-hardirq-v1-1-6398a52f8f02@linaro.org>

On 7/24/25 2:54 AM, André Draszik wrote:
> @@ -5656,19 +5689,39 @@ static int ufshcd_poll(struct Scsi_Host *shost, unsigned int queue_num)
>   	WARN_ONCE(completed_reqs & ~hba->outstanding_reqs,
>   		  "completed: %#lx; outstanding: %#lx\n", completed_reqs,
>   		  hba->outstanding_reqs);
> -	if (queue_num == UFSHCD_POLL_FROM_INTERRUPT_CONTEXT) {
> -		/* Do not complete polled requests from interrupt context. */
> +	if (time_limit) {
> +		/* Do not complete polled requests from hardirq context. */
>   		ufshcd_clear_polled(hba, &completed_reqs);
>   	}

This if-statement and the code inside the if-statement probably can be
left out. This if-statement was introduced at a time when the block
layer did not support completing polled requests from interrupt context.
I think that commit b99182c501c3 ("bio: add pcpu caching for non-polling
bio_put") enabled support for completing polled requests from interrupt
context. Since this patch touches that if-statement, how about removing
it with a separate patch that comes before this patch? Polling can be
enabled by adding --hipri=1 to the fio command line and by using an I/O
engine that supports polling, e.g. pvsync2 or io_uring.

Thanks,

Bart.

  parent reply	other threads:[~2025-07-24 16:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  9:54 André Draszik
2025-07-24 11:44 ` André Draszik
2025-07-24 11:54   ` Neil Armstrong
2025-07-24 13:38     ` André Draszik
2025-07-28 14:36       ` Manivannan Sadhasivam
2025-07-28 14:39         ` Manivannan Sadhasivam
2025-07-28 14:41           ` Neil Armstrong
2025-07-28 14:47             ` Manivannan Sadhasivam
2025-07-24 16:02 ` Bart Van Assche [this message]
2025-07-25 15:00   ` André Draszik
2025-07-28 14:42     ` Manivannan Sadhasivam
2025-07-28 14:49       ` Manivannan Sadhasivam

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=2e7c2be8-dc58-4e18-9297-e8690565583b@acm.org \
    --to=bvanassche@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andre.draszik@linaro.org \
    --cc=avri.altman@wdc.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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 \
    /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®