[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.23.453.2010231324510.6@nippy.intranet>
Date: Fri, 23 Oct 2020 13:44:01 +1100 (AEDT)
From: Finn Thain <fthain@...egraphics.com.au>
To: Tianxianting <tian.xianting@....com>
cc: "kashyap.desai@...adcom.com" <kashyap.desai@...adcom.com>,
"sumit.saxena@...adcom.com" <sumit.saxena@...adcom.com>,
"shivasharan.srikanteshwara@...adcom.com"
<shivasharan.srikanteshwara@...adcom.com>,
"jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"megaraidlinux.pdl@...adcom.com" <megaraidlinux.pdl@...adcom.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ
On Thu, 22 Oct 2020, Tianxianting wrote:
> I see, If we add this patch, we need to get all cpu arch that support
> nested interrupts.
>
I was just calling into question 1. the benefit (does it improve
performance?) and 2. the code style (is it less portable?).
It's really the style question that mostly interests me because I've had
to code around the nested interrupt situation before, and everytime it
comes up it makes me wonder about the necessity.
I was not trying to veto your patch. It is not my position to do that. If
Broadcom likes the patch, that's great.
Powered by blists - more mailing lists