From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: John Meneghini <jmeneghi@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
pheidologeton@protonmail.com, kernel@roadkil.net,
maokaman@gmail.com, Sagar.Biradar@microchip.com,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, thenzl@redhat.com,
mpatalan@redhat.com, Scott.Benesh@microchip.com,
Don.Brace@microchip.com, Tom.White@microchip.com,
Abhinav.Kuchibhotla@microchip.com
Subject: Re: [PATCH] [v2]aacraid: Reply queue mapping to CPUs based on IRQ affinity
Date: Mon, 10 Mar 2025 21:16:08 -0400 [thread overview]
Message-ID: <yq134fkjrlp.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <84a87c16-0738-460d-b83f-55f8181d536e@suse.de> (Hannes Reinecke's message of "Mon, 10 Mar 2025 17:44:14 +0100")
Hannes,
> Wouldn't it be an idea to check if we can make this a generic / blk-mq
> queue option instead of having each driver to implement the same
> functionality on it's own?
>
> Topic for LSF?
I would love to have a generic fix.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2025-03-11 1:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 17:33 [PATCH] [v2]aacraid: Reply queue mapping to CPUs based on IRQ affinity Sagar Biradar
2025-02-10 17:20 ` John Meneghini
2025-02-10 20:24 ` John Meneghini
2025-02-13 2:56 ` Martin K. Petersen
2025-02-13 21:26 ` Sagar.Biradar
[not found] ` <PH7PR11MB7570E9E65153C48BA7C5679EFAFF2@PH7PR11MB7570.namprd11.prod.outlook.com>
2025-02-13 21:31 ` Sagar.Biradar
2025-02-13 22:03 ` John Meneghini
2025-02-13 22:21 ` John Meneghini
2025-02-21 2:38 ` Martin K. Petersen
2025-02-24 21:15 ` John Meneghini
2025-03-10 16:44 ` Hannes Reinecke
2025-03-11 1:16 ` Martin K. Petersen [this message]
2025-03-12 1:52 ` John Meneghini
2025-03-25 0:16 ` Sagar.Biradar
2025-03-25 1:54 ` John Garry
2025-04-17 16:02 ` Sagar.Biradar
2025-04-22 6:42 ` Hannes Reinecke
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=yq134fkjrlp.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Abhinav.Kuchibhotla@microchip.com \
--cc=Don.Brace@microchip.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sagar.Biradar@microchip.com \
--cc=Scott.Benesh@microchip.com \
--cc=Tom.White@microchip.com \
--cc=hare@suse.de \
--cc=jmeneghi@redhat.com \
--cc=kernel@roadkil.net \
--cc=linux-scsi@vger.kernel.org \
--cc=maokaman@gmail.com \
--cc=mpatalan@redhat.com \
--cc=pheidologeton@protonmail.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 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.