aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/bnx2i/bnx2i_iscsi.c
diff options
context:
space:
mode:
authorMike Christie <michaelc@cs.wisc.edu>2010-02-10 16:51:45 -0600
committerJames Bottomley <James.Bottomley@suse.de>2010-02-17 13:40:10 -0600
commit92ed4d69934a1281abcc10c6a82274a04651a260 (patch)
tree731351eb3bd1c642dc8ed8b27389173e44998a77 /drivers/scsi/bnx2i/bnx2i_iscsi.c
parent9010b94636312c7fb12b591ef09e915f8f80bbd5 (diff)
downloadkernel_samsung_smdk4412-92ed4d69934a1281abcc10c6a82274a04651a260.zip
kernel_samsung_smdk4412-92ed4d69934a1281abcc10c6a82274a04651a260.tar.gz
kernel_samsung_smdk4412-92ed4d69934a1281abcc10c6a82274a04651a260.tar.bz2
[SCSI] libiscsi: reset cmd timer if cmds are making progress
This patch resets the cmd timer if cmds started before the timedout command are making progress. The idea is that the cmd probably timed out because we are trying to exeucte too many commands. If it turns out that the device the IO timedout on was bad or the cmd just got screwed up but other IO/devs were ok then we will will figure this out when the cmds ahead of the timed out one complete ok. This also fixes a bug where we were sort of detecting this by setting the last_timeout and last_xfer to the same value when the task was allocated. That caught the case where we never got to send any IO for it. However, if the problem had started right before we started the new task, then we were forced to wait an extra cmd timeout seconds to start the scsi eh. Signed-off-by: Mike Christie <michaelc@cs.wisc.edu> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/scsi/bnx2i/bnx2i_iscsi.c')
0 files changed, 0 insertions, 0 deletions