mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: "Sean A." <sean@ashe.io>,
	"James.Bottomley@hansenpartnership.com"
	<James.Bottomley@hansenpartnership.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: Fri, 20 Jun 2025 11:43:40 +0100	[thread overview]
Message-ID: <fcec4cd7-8e0a-4dca-a1b4-519b5e683c52@oracle.com> (raw)
In-Reply-To: <ntxbqgnwvjdxggl5hno7eqae6ccpzwoyule3gwo4pnb53h4jiy@qfvkb3ocdeef>

On 19/06/2025 20:35, Aaron Tomlin wrote:
> 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.
> Hi John,
> 
> I'm trying to understand this better. If I'm not mistaken, modifying
> /sys/block/[device]/queue/rq_affinity impacts where requests are processed.
> Could you clarify how this would prevent an IRQ from being delivered to an
> isolated CPU?

If you echo 2 > /sys/block/[device]/queue/rq_affinity, then completions 
will occur on the same CPU which their originated. And through taskset, 
if you keep the processes generating traffic on a certain group of CPUs, 
then other CPUs should not see any loading from those same processes.

I am assuming that there is a one-to-one CPU <-> HW queue relationship.

That's my unverified idea...

  reply	other threads:[~2025-06-20 10:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- 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=fcec4cd7-8e0a-4dca-a1b4-519b5e683c52@oracle.com \
    --to=john.g.garry@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=martin.petersen@oracle.com \
    --cc=mpi3mr-linuxdrv.pdl@broadcom.com \
    --cc=sean@ashe.io \
    --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®