mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: mpi3mr-linuxdrv.pdl@broadcom.com, kashyap.desai@broadcom.com,
	sumit.saxena@broadcom.com, sreekanth.reddy@broadcom.com,
	James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/1] scsi: mpi3mr: Introduce smp_affinity_enable module parameter
Date: Mon, 16 Jun 2025 16:51:37 -0400	[thread overview]
Message-ID: <yq15xgvz9z5.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20250601014056.128716-2-atomlin@atomlin.com> (Aaron Tomlin's message of "Sat, 31 May 2025 21:40:56 -0400")


> This patch introduces a new module parameter namely
> "smp_affinity_enable", to govern the application of system-wide IRQ
> affinity (with kernel boot-time parameter "irqaffinity") for MSI-X
> interrupts. By default, the default IRQ affinity mask will not be
> respected. Set smp_affinity_enable to 0 disables this behaviour.
> Consequently, preventing the auto-assignment of MSI-X IRQs.

Broadcom: Please review!

-- 
Martin K. Petersen

  reply	other threads:[~2025-06-16 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01  1:40 [RFC PATCH v2 0/1] " Aaron Tomlin
2025-06-01  1:40 ` [RFC PATCH v2 1/1] " Aaron Tomlin
2025-06-16 20:51   ` Martin K. Petersen [this message]
2025-06-17  7:18   ` John Garry
2025-06-17 16:34 Sean A.
2025-06-18  6:49 ` John Garry
2025-06-18 15:53   ` Sean A.
2025-06-19 19:35   ` Aaron Tomlin
2025-06-20 10:43     ` John Garry
2025-06-23  5:17   ` Christoph Hellwig
2025-06-24 14:29     ` Daniel Wagner
2025-06-25 13:03       ` Aaron Tomlin
2025-07-01 13:54         ` Daniel Wagner
2025-07-02  0:30           ` Aaron Tomlin

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=yq15xgvz9z5.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=atomlin@atomlin.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpi3mr-linuxdrv.pdl@broadcom.com \
    --cc=sreekanth.reddy@broadcom.com \
    --cc=sumit.saxena@broadcom.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®