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
