diff options
| author | Ren Mingxin | 2013-11-11 13:44:56 +0100 |
|---|---|---|
| committer | James Bottomley | 2013-12-19 16:39:02 +0100 |
| commit | bb3b621a33d60fc2baddf31597ade01243e00a2c (patch) | |
| tree | 73fae0429ce43ce37845e207cb36da2e8f54d42c /Documentation/scsi/scsi_mid_low_api.txt | |
| parent | [SCSI] Unlock accesses to eh_deadline (diff) | |
| download | kernel-qcow2-linux-bb3b621a33d60fc2baddf31597ade01243e00a2c.tar.gz kernel-qcow2-linux-bb3b621a33d60fc2baddf31597ade01243e00a2c.tar.xz kernel-qcow2-linux-bb3b621a33d60fc2baddf31597ade01243e00a2c.zip | |
[SCSI] Set the minimum valid value of 'eh_deadline' as 0
The former minimum valid value of 'eh_deadline' is 1s, which means
the earliest occasion to shorten EH is 1 second later since a
command is failed or timed out. But if we want to skip EH steps
ASAP, we have to wait until the first EH step is finished. If the
duration of the first EH step is long, this waiting time is
excruciating. So, it is necessary to accept 0 as the minimum valid
value for 'eh_deadline'.
According to my test, with Hannes' patchset 'New EH command timeout
handler' as well, the minimum IO time is improved from 73s
(eh_deadline = 1) to 43s(eh_deadline = 0) when commands are timed
out by disabling RSCN and target port.
Signed-off-by: Ren Mingxin <renmx@cn.fujitsu.com>
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'Documentation/scsi/scsi_mid_low_api.txt')
0 files changed, 0 insertions, 0 deletions