From: Finn Thain <fthain@telegraphics.com.au>
To: Tianxianting <tian.xianting@h3c.com>
Cc: "kashyap.desai@broadcom.com" <kashyap.desai@broadcom.com>,
"sumit.saxena@broadcom.com" <sumit.saxena@broadcom.com>,
"shivasharan.srikanteshwara@broadcom.com"
<shivasharan.srikanteshwara@broadcom.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"megaraidlinux.pdl@broadcom.com" <megaraidlinux.pdl@broadcom.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ
Date: Thu, 22 Oct 2020 14:29:16 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.23.453.2010221424390.6@nippy.intranet> (raw)
In-Reply-To: <9923f28dd2b34499a17c53e8fa33f1ca@h3c.com>
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.
next prev parent reply other threads:[~2020-10-22 3:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 6:45 [PATCH] scsi: megaraid_sas: use spin_lock() in hard IRQ Xianting Tian
2020-10-22 2:25 ` Finn Thain
2020-10-22 2:59 ` Tianxianting
2020-10-22 3:29 ` Finn Thain [this message]
2020-10-22 10:09 ` Tianxianting
2020-10-23 2:44 ` Finn Thain
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=alpine.LNX.2.23.453.2010221424390.6@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=jejb@linux.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.com \
--cc=tian.xianting@h3c.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;
as well as URLs for NNTP newsgroup(s).