linux-kernel - Re: [PATCH for-next 00/32] spin lock usage optimization for SCSI drivers

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <31cd807d-3d0-ed64-60d-fde32cb3833c@telegraphics.com.au>
Date:   Mon, 8 Feb 2021 18:57:12 +1100 (AEDT)
From:   Finn Thain <fthain@...egraphics.com.au>
To:     Xiaofei Tan <tanxiaofei@...wei.com>
cc:     jejb@...ux.ibm.com, martin.petersen@...cle.com,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
        linuxarm@...neuler.org
Subject: Re: [PATCH for-next 00/32] spin lock usage optimization for SCSI
 drivers

On Sun, 7 Feb 2021, Xiaofei Tan wrote:

> Replace spin_lock_irqsave with spin_lock in hard IRQ of SCSI drivers. 
> There are no function changes, but may speed up if interrupt happen too 
> often.

This change doesn't necessarily work on platforms that support nested 
interrupts.

Were you able to measure any benefit from this change on some other 
platform?

Please see also,
https://lore.kernel.org/linux-scsi/89c5cb05cb844939ae684db0077f675f@h3c.com/