From: Paul Menzel <pmenzel+linux-scsi@molgen.mpg.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Ming Lei <ming.lei@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
it+linux-scsi@molgen.mpg.de,
Adaptec OEM Raid Solutions <aacraid@microsemi.com>,
linux-scsi@vger.kernel.org,
Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>,
Dave Carroll <david.carroll@microsemi.com>
Subject: Re: [PATCH] Revert "genirq/affinity: assign vectors to all possible CPUs"
Date: Mon, 1 Oct 2018 14:43:36 +0200 [thread overview]
Message-ID: <f5dde120-2d14-a7e5-8402-401f117b8c38@molgen.mpg.de> (raw)
In-Reply-To: <20181001123508.GA3415@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Dear Christoph,
On 10/01/18 14:35, Christoph Hellwig wrote:
> On Mon, Oct 01, 2018 at 02:33:07PM +0200, Paul Menzel wrote:
>> Date: Wed, 29 Aug 2018 17:28:45 +0200
>>
>> This reverts commit ef86f3a72adb8a7931f67335560740a7ad696d1d.
>
> This seems rather odd. If at all you'd revert the patch adding the
> PCI_IRQ_AFFINITY to aacraid, not core infrastructure.
Thank you for the suggestion, but that flag was added in 2016
to the aacraid driver.
> commit 0910d8bbdd99856af1394d3d8830955abdefee4a
> Author: Hannes Reinecke <hare@suse.de>
> Date: Tue Nov 8 08:11:30 2016 +0100
>
> scsi: aacraid: switch to pci_alloc_irq_vectors
>
> Use pci_alloc_irq_vectors and drop the hand-crafted interrupt affinity
> routines.
So what would happen, if `PCI_IRQ_AFFINITY` was removed? Will the
system still work with the same performance?
As far as I understood, the no regression policy is there for
exactly that reason, and it shouldn’t matter if it’s core
infrastructure or not. As written, I have no idea, and just know
reverting the commit in question fixes the problem here. So I’ll
gladly test other solutions to fix this issue.
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2018-10-01 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 13:21 aacraid: Regression in 4.14.56 with *genirq/affinity: assign vectors to all possible CPUs* Paul Menzel
2018-08-10 13:36 ` Greg Kroah-Hartman
2018-08-10 14:11 ` Paul Menzel
2018-08-10 15:55 ` Greg Kroah-Hartman
2018-08-11 8:14 ` Paul Menzel
2018-08-11 13:50 ` Greg Kroah-Hartman
2018-08-12 8:35 ` Paul Menzel
2018-08-13 3:32 ` Ming Lei
2018-08-16 17:09 ` Paul Menzel
2018-09-11 10:53 ` Paul Menzel
2018-10-01 12:33 ` [PATCH] Revert "genirq/affinity: assign vectors to all possible CPUs" Paul Menzel
2018-10-01 12:35 ` Christoph Hellwig
2018-10-01 12:43 ` Paul Menzel [this message]
2018-10-01 15:59 ` Paul Menzel
2018-10-15 12:17 ` Paul Menzel
2018-10-15 13:21 ` Greg Kroah-Hartman
2018-10-17 15:00 ` Paul Menzel
2018-10-30 15:30 ` Paul Menzel
2018-10-08 2:11 ` Ming Lei
2018-10-08 7:56 ` IT (Donald Buczek)
2019-02-18 11:40 ` aacraid: Regression in 4.14.56 with *genirq/affinity: assign vectors to all possible CPUs* Greg Kroah-Hartman
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=f5dde120-2d14-a7e5-8402-401f117b8c38@molgen.mpg.de \
--to=pmenzel+linux-scsi@molgen.mpg.de \
--cc=RaghavaAditya.Renukunta@microsemi.com \
--cc=aacraid@microsemi.com \
--cc=david.carroll@microsemi.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=it+linux-scsi@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=stable@vger.kernel.org \
/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).