1. 07 12月, 2009 2 次提交
  2. 22 9月, 2009 1 次提交
  3. 11 9月, 2009 1 次提交
  4. 07 7月, 2009 1 次提交
  5. 16 6月, 2009 1 次提交
  6. 12 6月, 2009 2 次提交
  7. 26 3月, 2009 3 次提交
  8. 09 1月, 2009 1 次提交
  9. 21 10月, 2008 1 次提交
  10. 11 10月, 2008 1 次提交
  11. 01 8月, 2008 1 次提交
  12. 15 5月, 2008 1 次提交
  13. 17 4月, 2008 1 次提交
  14. 26 1月, 2008 1 次提交
    • S
      [S390] dasd: add hyper PAV support to DASD device driver, part 1 · 8e09f215
      Stefan Weinhuber 提交于
      Parallel access volumes (PAV) is a storage server feature, that allows
      to start multiple channel programs on the same DASD in parallel. It
      defines alias devices which can be used as alternative paths to the
      same disk. With the old base PAV support we only needed rudimentary
      functionality in the DASD device driver. As the mapping between base
      and alias devices was static, we just had to export an identifier
      (uid) and could leave the combining of devices to external layers
      like a device mapper multipath.
      Now hyper PAV removes the requirement to dedicate alias devices to
      specific base devices. Instead each alias devices can be combined with
      multiple base device on a per request basis. This requires full
      support by the DASD device driver as now each channel program itself
      has to identify the target base device.
      The changes to the dasd device driver and the ECKD discipline are:
      - Separate subchannel device representation (dasd_device) from block
        device representation (dasd_block). Only base devices are block
        devices.
      - Gather information about base and alias devices and possible
        combinations.
      - For each request decide which dasd_device should be used (base or
        alias) and build specific channel program.
      - Support summary unit checks, which allow the storage server to
        upgrade / downgrade between base and hyper PAV at runtime (support
        is mandatory).
      Signed-off-by: NStefan Weinhuber <wein@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      8e09f215
  15. 12 10月, 2007 1 次提交
  16. 24 7月, 2007 1 次提交
  17. 05 5月, 2007 1 次提交
  18. 06 2月, 2007 1 次提交
  19. 08 12月, 2006 2 次提交
  20. 20 9月, 2006 1 次提交
    • M
      [S390] dasd deadlock after state change pending interrupt. · a00bfd71
      Martin Schwidefsky 提交于
      The dasd_device_from_cdev function is called from interrupt context
      to get the struct dasd_device associated with a ccw device. The
      driver_data of the ccw device points to the dasd_devmap structure
      which contains the pointer to the dasd_device structure. The lock
      that protects the dasd_devmap structure is acquire with out irqsave.
      To prevent the deadlock in dasd_device_from_cdev if it is called
      from interrupt context the dependency to the dasd_devmap structure
      needs to be removed. Let the driver_data of the ccw device point
      to the dasd_device structure directly and use the ccw device lock
      to protect the access.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      a00bfd71
  21. 29 6月, 2006 2 次提交
  22. 27 6月, 2006 1 次提交
  23. 28 4月, 2006 1 次提交
  24. 24 3月, 2006 4 次提交
  25. 09 3月, 2006 1 次提交
  26. 21 2月, 2006 2 次提交
  27. 04 2月, 2006 1 次提交
  28. 02 2月, 2006 1 次提交
  29. 11 1月, 2006 1 次提交
  30. 07 1月, 2006 1 次提交