aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/s390/block/dasd_diag.c
diff options
context:
space:
mode:
authorStefan Weinhuber <wein@de.ibm.com>2010-08-09 18:12:59 +0200
committerMartin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com>2010-08-09 18:12:54 +0200
commitf932bcea6b7317312ab38df12a84710fc6c67a81 (patch)
tree6476fb6c8423ee65bc8b73182436ccfc7361ed05 /drivers/s390/block/dasd_diag.c
parent[S390] topology: use default MC domain initializer (diff)
downloadlinux-dev-f932bcea6b7317312ab38df12a84710fc6c67a81.tar.xz
linux-dev-f932bcea6b7317312ab38df12a84710fc6c67a81.zip
[S390] dasd: allocate fallback cqr for reserve/release
The DASD reserve and release ioctls use the preallocated memory pool of the respective device to build their CCW requests. However, when the device is busy, the pool may already be empty and the ioctl fails. Usually this can be recovered by calling the ioctl again, but in a situation in which we need to issue an unconditional reserve to make a device operational again, this would be not recoverable. To avoid a failure due to lack of memory, DASD device driver will preallocate enough memory for a single reserve/release request, which can be used if normal allocation fails. Signed-off-by: Stefan Weinhuber <wein@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/s390/block/dasd_diag.c')
0 files changed, 0 insertions, 0 deletions