From: Christoph Hellwig <hch@infradead.org>
To: John Garry <john.g.garry@oracle.com>, Daniel Wagner <wagi@kernel.org>
Cc: "Sean A." <sean@ashe.io>,
"James.Bottomley@hansenpartnership.com"
<James.Bottomley@hansenpartnership.com>,
"atomlin@atomlin.com" <atomlin@atomlin.com>,
"kashyap.desai@broadcom.com" <kashyap.desai@broadcom.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"mpi3mr-linuxdrv.pdl@broadcom.com"
<mpi3mr-linuxdrv.pdl@broadcom.com>,
"sreekanth.reddy@broadcom.com" <sreekanth.reddy@broadcom.com>,
"sumit.saxena@broadcom.com" <sumit.saxena@broadcom.com>
Subject: Re: [RFC PATCH v2 1/1] scsi: mpi3mr: Introduce smp_affinity_enable module parameter
Date: Sun, 22 Jun 2025 22:17:51 -0700 [thread overview]
Message-ID: <aFjjf3qbuEOeWUjt@infradead.org> (raw)
In-Reply-To: <077ffc15-f949-41d4-a13b-4949990ba830@oracle.com>
On Wed, Jun 18, 2025 at 07:49:16AM +0100, John Garry wrote:
> BTW, if you use taskset to set the affinity of a process and ensure that
> /sys/block/xxx/queue/rq_affinity is set so that we complete on same CPU as
> submitted, then I thought that this would ensure that interrupts are not
> bothering other CPUs.
The RT folks want to not even have interrupts on the application CPUs.
That's perfectly reasonable and a common request. Why doing driver
hacks as in this patch and many others is so completely insane. Instead
we need common functionality for that. The core irq layer has added
them for managed interrupts, and Daniel has been working on the blk-mq side
for a while.
next prev parent reply other threads:[~2025-06-23 5:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 16:34 [RFC PATCH v2 1/1] scsi: mpi3mr: Introduce smp_affinity_enable module parameter 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2025-06-17 7:18 ` 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=aFjjf3qbuEOeWUjt@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=atomlin@atomlin.com \
--cc=john.g.garry@oracle.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpi3mr-linuxdrv.pdl@broadcom.com \
--cc=sean@ashe.io \
--cc=sreekanth.reddy@broadcom.com \
--cc=sumit.saxena@broadcom.com \
--cc=wagi@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 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.