kernel_optimize_test/drivers/s390
Stefan Weinhuber 1afcfd5948 [S390] dasd: fix expiration handling for recovery requests
The 'expires' value of a ccw requests defines how long the device
driver should wait for a response from the evice after the request has
been submitted to the channel subsystem. After the expiration time
(e.g. 30 seconds) the waiting request will be cancelled and started
again. This protects the DASD devices from beeing blocked by errors
that cause the answering I/O interrupt to be lost.

In case of error recovery requests, this 'expires' value used to be
set to 0, so in case of a lost interrupt, such a recovery request
would never expire and block the device. To prevent this kind of
problem, all recovery requests need to have an expires value > 0 as
well. If not specified otherwise, this should be the same expires
value as for the original request.

Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2011-12-27 11:27:13 +01:00
..
block [S390] dasd: fix expiration handling for recovery requests 2011-12-27 11:27:13 +01:00
char [S390] zfcpdump: Do not initialize zfcpdump in kdump mode 2011-11-14 11:19:09 +01:00
cio [S390] qdio: fix qdio_allocate_aob() declaration 2011-12-27 11:27:10 +01:00
crypto [S390] zcrypt: Fix error return codes. 2011-12-27 11:27:13 +01:00
kvm Merge branch 'modsplit-Oct31_2011' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux 2011-11-06 19:44:47 -08:00
net qeth: Reduce CPU consumption through less SIGA-r calls 2011-11-16 17:28:20 -05:00
scsi [SCSI] zfcp: return early from slave_destroy if slave_alloc returned early 2011-12-14 15:40:43 +04:00
Makefile [S390] split/move machine check handler code 2009-03-26 15:24:10 +01:00