[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.23.453.2010221424390.6@nippy.intranet>
Date: Thu, 22 Oct 2020 14:29:16 +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:
> Do you mean Megasas raid can be used in m68k arch?
m68k is one example of an architecture on which the unstated assumptions
in your patch would be invalid. Does this help to clarify what I wrote?
If Megasas raid did work on m68k, I'm sure it could potentially benefit
from the theoretical performance improvement from your patch.
So perhaps you would consider adding support for slower CPUs like m68k.
Powered by blists - more mailing lists