From: John Garry <john.g.garry@oracle.com>
To: Sagar.Biradar@microchip.com, Don.Brace@microchip.com,
Gilbert.Wu@microchip.com, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, jejb@linux.ibm.com,
brking@linux.vnet.ibm.com, stable@vger.kernel.org,
Tom.White@microchip.com
Subject: Re: [PATCH] aacraid: reply queue mapping to CPUs based of IRQ affinity
Date: Fri, 14 Apr 2023 08:20:47 +0100 [thread overview]
Message-ID: <b4650194-0f2f-8850-fb98-962354c1ff9f@oracle.com> (raw)
In-Reply-To: <BYAPR11MB3606A019F9557536CB0D47C9FA989@BYAPR11MB3606.namprd11.prod.outlook.com>
On 13/04/2023 22:52, Sagar.Biradar@microchip.com wrote:
[snip]
> Yes we have reserved commands, that originate from within the driver.
> We rely on the reply_map mechanism (from the original patch) to get interrupt vector for the reserved commands too.
>
>
> Thanks
> Sagar
>
>
>
>
> Also, there is this patch which addresses the concerns John Garry raised.
> https://urldefense.com/v3/__https://lore.kernel.org/lkml/20220929033428.25948-1-mj0123.lee@samsung.com/T/__;!!ACWV5N9M2RV99hQ!Jjh5jXadoTBK0R4UONFNOssLSRfzaOA9yV2ENIlArRzHEe6ylDxDEIwIzs9nzUOkLmgVC-B2Nfd_sjeho995VACy5O0qoA$
>
> This patch explains how the coordination happens when a CPU goes offline.
> IPI can be read InterProcessor Interrupt.
> The request shall be completed from the CPU where it is running when the original CPU goes offline.
>
> Thanks
> Sagar
Can you please use standard mailing list practices in your replies, i.e.
quote original mail in the reply here? I don't know what was added to
the thread in this latest reply.
Thanks,
John
next prev parent reply other threads:[~2023-04-14 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 21:41 [PATCH] aacraid: reply queue mapping to CPUs based of IRQ affinity Sagar Biradar
2023-03-29 7:08 ` John Garry
2023-04-10 21:17 ` Sagar.Biradar
2023-04-12 9:38 ` John Garry
2023-04-12 19:29 ` Sagar.Biradar
2023-04-13 21:52 ` Sagar.Biradar
2023-04-14 7:20 ` John Garry [this message]
2023-04-14 20:07 ` Sagar.Biradar
2023-04-18 16:36 ` Sagar.Biradar
2023-04-18 17:12 ` James Bottomley
2023-04-18 23:55 ` Sagar.Biradar
2023-04-19 7:42 ` 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=b4650194-0f2f-8850-fb98-962354c1ff9f@oracle.com \
--to=john.g.garry@oracle.com \
--cc=Don.Brace@microchip.com \
--cc=Gilbert.Wu@microchip.com \
--cc=Sagar.Biradar@microchip.com \
--cc=Tom.White@microchip.com \
--cc=brking@linux.vnet.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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