From: John Garry <john.g.garry@oracle.com>
To: John Meneghini <jmeneghi@redhat.com>,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
aacraid@microsemi.com, corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
thenzl@redhat.com, Scott.Benesh@microchip.com,
Don.Brace@microchip.com, Tom.White@microchip.com,
Abhinav.Kuchibhotla@microchip.com, sagar.biradar@microchip.com,
mpatalan@redhat.com
Subject: Re: [PATCH v3] scsi: aacraid: Fix reply queue mapping to CPUs based on IRQ affinity
Date: Thu, 19 Jun 2025 11:46:44 +0100 [thread overview]
Message-ID: <682ff953-9130-4920-a9f2-88dfd6718be1@oracle.com> (raw)
In-Reply-To: <20250618192427.3845724-1-jmeneghi@redhat.com>
On 18/06/2025 20:24, John Meneghini wrote:
> From: Sagar Biradar <sagar.biradar@microchip.com>
>
> From: Sagar Biradar <sagar.biradar@microchip.com>
>
> This patch fixes a bug in the original path that caused I/O hangs. The
> I/O hangs were because of an MSIx vector not having a mapped online CPU
> upon receiving completion.
>
> This patch enables Multi-Q support in the aacriad driver. Multi-Q support
> in the driver is needed to support CPU offlining.
I assume that you mean "safe" CPU offlining.
It seems to me that in all cases we use queue interrupt affinity
spreading and managed interrupts for MSIX, right?
See aac_define_int_mode() -> pci_alloc_irq_vectors(..., PCI_IRQ_MSIX |
PCI_IRQ_AFFINITY);
But then for this non- Multi-Q support, the queue seems to be chosen
based on a round-robin approach in the driver. That round-robin comes
from how fib.vector_no is assigned in aac_fib_vector_assign(). If this
is the case, then why are managed interrupts being used for this non-
Multi-Q support at all?
I may be wrong about this. That driver is hard to understand with so
many knobs.
next prev parent reply other threads:[~2025-06-19 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 19:24 [PATCH v3] scsi: aacraid: Fix reply queue mapping to CPUs based on IRQ affinity John Meneghini
2025-06-18 19:37 ` John Meneghini
2025-06-19 10:46 ` John Garry [this message]
2025-07-10 6:49 ` Sagar.Biradar
2025-07-10 8:12 ` John Garry
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=682ff953-9130-4920-a9f2-88dfd6718be1@oracle.com \
--to=john.g.garry@oracle.com \
--cc=Abhinav.Kuchibhotla@microchip.com \
--cc=Don.Brace@microchip.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Scott.Benesh@microchip.com \
--cc=Tom.White@microchip.com \
--cc=aacraid@microsemi.com \
--cc=corbet@lwn.net \
--cc=jmeneghi@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatalan@redhat.com \
--cc=sagar.biradar@microchip.com \
--cc=thenzl@redhat.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;
as well as URLs for NNTP newsgroup(s).