On 12/06/2017 10:45, Arnd Bergmann wrote:
On Mon, Jun 12, 2017 at 10:26 AM, John Garry wrote:
On 10/06/2017 21:44, kbuild test robot wrote:
I don't think that reusing flags variable is in error, as there would be no
nested spinlock at this point within the function.
If it is not recommended
On Mon, Jun 12, 2017 at 10:26 AM, John Garry wrote:
> On 10/06/2017 21:44, kbuild test robot wrote:
>
>
> I don't think that reusing flags variable is in error, as there would be no
> nested spinlock at this point within the function.
>
> If it is not recommended or not permitted to reuse flags va
On 10/06/2017 21:44, kbuild test robot wrote:
Hi Xiang,
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on v4.12-rc4 next-20170609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/lin
Hi Xiang,
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on v4.12-rc4 next-20170609]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/John-Garry/hisi_sas-hip08-support/201
From: Xiang Chen
Currently hisi_hba.lock is locked to deliver and receive a
command to/from any hw queue. This causes much
contention at high data-rates.
To boost performance, lock on a per queue basis for
sending and receiving commands to/from hw.
Certain critical regions still need to be lock
5 matches
Mail list logo
