Searched hist:f4ac1d0255748fe0f8e128a26b1c29490cae5c08 (Results 1 – 3 of 3) sorted by relevance
| /linux/drivers/s390/block/ |
| H A D | dasd_eckd.h | diff f4ac1d0255748fe0f8e128a26b1c29490cae5c08 Mon Dec 07 12:51:53 CET 2009 Stefan Weinhuber <wein@de.ibm.com> [S390] dasd: let device initialization wait for LCU setup
The first DASD that is set online for a specific logical control unit
has to do certain setup steps on the storage server to make full use
of it, for example it will enable PAV.
The features and characteristics reported by the storage server will
depend on this setup, so all other devices on the same LCU will need
to wait for the setup to be finished.
Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| H A D | dasd_alias.c | diff f4ac1d0255748fe0f8e128a26b1c29490cae5c08 Mon Dec 07 12:51:53 CET 2009 Stefan Weinhuber <wein@de.ibm.com> [S390] dasd: let device initialization wait for LCU setup
The first DASD that is set online for a specific logical control unit
has to do certain setup steps on the storage server to make full use
of it, for example it will enable PAV.
The features and characteristics reported by the storage server will
depend on this setup, so all other devices on the same LCU will need
to wait for the setup to be finished.
Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
| H A D | dasd_eckd.c | diff f4ac1d0255748fe0f8e128a26b1c29490cae5c08 Mon Dec 07 12:51:53 CET 2009 Stefan Weinhuber <wein@de.ibm.com> [S390] dasd: let device initialization wait for LCU setup
The first DASD that is set online for a specific logical control unit
has to do certain setup steps on the storage server to make full use
of it, for example it will enable PAV.
The features and characteristics reported by the storage server will
depend on this setup, so all other devices on the same LCU will need
to wait for the setup to be finished.
Signed-off-by: Stefan Weinhuber <wein@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|