linux-kernel - Re: [GIT PULL] final round of SCSI updates for the 5.2+ merge window

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]

Message-ID: <yq14l3gx49d.fsf@oracle.com>
Date:   Sat, 20 Jul 2019 08:46:38 -0400
From:   "Martin K. Petersen" <martin.petersen@...cle.com>
To:     Ming Lei <tom.leiming@...il.com>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-scsi <linux-scsi@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>
Subject: Re: [GIT PULL] final round of SCSI updates for the 5.2+ merge window


Hi Ming!

>> Christoph Hellwig (8):
>>       scsi: megaraid_sas: set an unlimited max_segment_size
>>       scsi: mpt3sas: set an unlimited max_segment_size for SAS 3.0 HBAs
>>       scsi: IB/srp: set virt_boundary_mask in the scsi host
>>       scsi: IB/iser: set virt_boundary_mask in the scsi host
>>       scsi: storvsc: set virt_boundary_mask in the scsi host template
>>       scsi: ufshcd: set max_segment_size in the scsi host template
>>       scsi: core: take the DMA max mapping size into account
>
> It has been observed on NVMe the above approach("take the DMA max
> mapping size into account") causes performance regression, so I'd
> suggest to fix dma_max_mapping_size() first.

Christoph specifically asked me to queue these up. I presume the swiotlb
tweak is going through his DMA tree and it is therefore orthogonal to
the SCSI changes.

I do think it's important that we get these fixed up in 5.3. And given
that we're on the eve of the merge window, the time to get these changes
merged is now. I'd hate to see them miss another release...

-- 
Martin K. Petersen	Oracle Linux Engineering