diff options
| author | Fedor Loshakov <[email protected]> | 2018-11-29 13:09:56 +0100 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2018-12-07 21:36:40 -0500 |
| commit | 636db60b8e910760c283b7aa928efcc580c1f574 (patch) | |
| tree | 5fcb77acc5bbdff913c0fbc7f304a25b60c50ddf /include/linux/timerqueue.h | |
| parent | 1ff2d8c43bc2ac78470033eae2947aec0c2e8cb6 (diff) | |
scsi: zfcp: make DIX experimental, disabled, and independent of DIF
Introduce separate zfcp module parameters to individually select support
for: DIF which should work (zfcp.dif, which used to be DIF+DIX, disabled)
or DIX+DIF which can cause trouble (zfcp.dix, new, disabled).
If DIX is enabled, we warn on zfcp driver initialization. As before, this
also reduces the maximum I/O request size to half, to support the worst
case of merged single sector requests with one protection data scatter
gather element per sector. This can impact the maximum throughput.
In DIF-only mode (zfcp.dif=1 zfcp.dix=0), we can use the full maximum I/O
request size as there is no protection data for zfcp.
Signed-off-by: Steffen Maier <[email protected]>
Signed-off-by: Fedor Loshakov <[email protected]>
Reviewed-by: Jens Remus <[email protected]>
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions