From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "bvanassche@acm.org" <bvanassche@acm.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"vamshigajjela@google.com" <vamshigajjela@google.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"chenyuan0y@gmail.com" <chenyuan0y@gmail.com>,
"ping.gao@samsung.com" <ping.gao@samsung.com>,
"alok.a.tiwari@oracle.com" <alok.a.tiwari@oracle.com>
Subject: Re: [PATCH 2/3] ufs: core: Introduce ufshcd_mcq_poll_cqe_lock_n()
Date: Wed, 1 Apr 2026 13:11:14 +0000 [thread overview]
Message-ID: <3d2ed2d4027f508c48897c40d11d0cc905568feb.camel@mediatek.com> (raw)
In-Reply-To: <a043946b-14e7-43da-8b68-dc47a08c12ff@acm.org>
On Tue, 2026-03-31 at 12:31 -0700, Bart Van Assche wrote:
> No, because the completion queue head is read before processing
> completion queue entries starts. No matter how many completions are
> pushed onto the completion queue while ufshcd_mcq_poll_cqe_lock() is
> in progress, it won't process more than (hwq->max_entries - 1)
> because
> that's the maximum difference between the tail and the head pointers.
>
> Thanks,
>
> Bart.
Hi Bart,
Yes, I got it. But I think you mean that "tail" is read
before processing, right?
Thanks
Peter
next prev parent reply other threads:[~2026-04-01 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 18:33 [PATCH 0/3] Reduce interrupt latency Bart Van Assche
2026-03-30 18:33 ` [PATCH 1/3] ufs: core: Fix ufshcd_mcq_force_compl_one() Bart Van Assche
2026-03-31 9:41 ` Peter Wang (王信友)
2026-03-31 19:29 ` Bart Van Assche
2026-04-01 13:10 ` Peter Wang (王信友)
2026-04-01 15:51 ` Bart Van Assche
2026-04-02 7:19 ` Peter Wang (王信友)
2026-03-30 18:33 ` [PATCH 2/3] ufs: core: Introduce ufshcd_mcq_poll_cqe_lock_n() Bart Van Assche
2026-03-31 9:43 ` Peter Wang (王信友)
2026-03-31 19:31 ` Bart Van Assche
2026-04-01 13:11 ` Peter Wang (王信友) [this message]
2026-04-01 15:51 ` Bart Van Assche
2026-04-02 7:20 ` Peter Wang (王信友)
2026-03-30 18:33 ` [PATCH 3/3] ufs: qcom: Reduce interrupt latency Bart Van Assche
2026-03-31 7:09 ` Manivannan Sadhasivam
2026-03-31 19:44 ` Bart Van Assche
2026-04-04 3:11 ` Manivannan Sadhasivam
2026-04-06 16:02 ` Bart Van Assche
2026-03-30 18:36 ` [PATCH 0/3] " Bart Van Assche
2026-03-31 2:01 ` Can Guo
2026-04-07 8:20 ` Xiaosen
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=3d2ed2d4027f508c48897c40d11d0cc905568feb.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alok.a.tiwari@oracle.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=chenyuan0y@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ping.gao@samsung.com \
--cc=vamshigajjela@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