All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Eugen Hristev" <ehristev@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI: iproc-msi: Removed potentially endless loop handling MSI events
Date: Tue, 03 Nov 2026 21:24:05 +0000	[thread overview]
Message-ID: <sashiko-outbox-196049@kernel.org> (raw)
In-Reply-To: <20261103-iproc-irq-v2-1-dc7223df35fc@kernel.org>

> The iProc MSI chained handler rereads the event queue tail after each
> batch and keeps processing until the queue is empty. A continuously fed
> queue can therefore keep the CPU in the handler indefinitely, starving
> other interrupts and causing RCU stalls under heavy Ethernet traffic.
> 
> To fix this scenario, remove the loop that keeps reading the head and
> the tail until there are no more pending events. Read the head and tail
> only once and process only the events recorded in that snapshot.
> Update the head before returning. Events arriving during processing
> remain queued for a subsequent parent interrupt, allowing other handlers
> to run without imposing an arbitrary event limit.
> 
> Discovered while testing it with an Ethernet NIC, when too many MSI
> interrupts come in, CPU might get starved:
> 
> [ ... ]
> 
> With this one loop approach, IRQ handler will complete and continue
> to serve MSI events on the next handler invocation.
> 
> Signed-off-by: Eugen Hristev <ehristev@kernel.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261103-iproc-irq-v2-1-dc7223df35fc@kernel.org?part=1


      reply	other threads:[~2026-11-03 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 21:20 [PATCH v2] PCI: iproc-msi: Removed potentially endless loop handling MSI events Eugen Hristev
2026-11-03 21:24 ` sashiko-bot [this message]

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=sashiko-outbox-196049@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ehristev@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.