lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 22 Oct 2020 10:09:00 +0000
From:   Tianxianting <tian.xianting@....com>
To:     Finn Thain <fthain@...egraphics.com.au>
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

Yes, thanks
I see, If we add this patch, we need to get all cpu arch that support nested interrupts.

-----Original Message-----
From: Finn Thain [mailto:fthain@...egraphics.com.au] 
Sent: Thursday, October 22, 2020 11:29 AM
To: tianxianting (RD) <tian.xianting@....com>
Cc: kashyap.desai@...adcom.com; sumit.saxena@...adcom.com; shivasharan.srikanteshwara@...adcom.com; jejb@...ux.ibm.com; martin.petersen@...cle.com; megaraidlinux.pdl@...adcom.com; linux-scsi@...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

Powered by Openwall GNU/*/Linux Powered by OpenVZ