Re: [PATCH 0/3] hisi_sas: device id/IPTT collision workaround

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "John" == John Garry <john.garry@xxxxxxxxxx> writes:

John> This patchset introduces a workaround to a hw quirk in the
John> HiSilicon SAS controller v2 hw.

John> The quirk is as follows: When a SATA and SAS frame arrives at the
John> host at the same time the frames may be swapped under this
John> condition: SATA device id bit [10:0] == SAS frame IPTT bit [10:0]
John> The workaround is to ensure these 2 values never match. The
John> workaround algorithm is as follows: - SATA device id bit0 always 0
John> - SATA IPTT has no restriction - SAS IPTT bit0 always 1 - SAS
John> device id has no restriction

John> The major restriction of this workaround is the SAS IPTT range is
John> halved, but this should be ok as testing has shown that even using
John> half the IPTT range does not affect performance.

Applied to 4.7/scsi-queue.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux