1. 26 3月, 2009 4 次提交
  2. 09 1月, 2009 1 次提交
  3. 25 12月, 2008 1 次提交
  4. 13 10月, 2008 1 次提交
    • M
      [SCSI] block: separate failfast into multiple bits. · 6000a368
      Mike Christie 提交于
      Multipath is best at handling transport errors. If it gets a device
      error then there is not much the multipath layer can do. It will just
      access the same device but from a different path.
      
      This patch breaks up failfast into device, transport and driver errors.
      The multipath layers (md and dm mutlipath) only ask the lower levels to
      fast fail transport errors. The user of failfast, read ahead, will ask
      to fast fail on all errors.
      
      Note that blk_noretry_request will return true if any failfast bit
      is set. This allows drivers that do not support the multipath failfast
      bits to continue to fail on any failfast error like before. Drivers
      like scsi that are able to fail fast specific errors can check
      for the specific fail fast type. In the next patch I will convert
      scsi.
      Signed-off-by: NMike Christie <michaelc@cs.wisc.edu>
      Cc: Jens Axboe <jens.axboe@oracle.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      6000a368
  5. 11 10月, 2008 3 次提交
  6. 01 8月, 2008 1 次提交
  7. 17 7月, 2008 1 次提交
  8. 14 7月, 2008 1 次提交
  9. 17 4月, 2008 1 次提交
  10. 26 1月, 2008 2 次提交
    • 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
    • J
      [S390] drivers/s390/: Spelling fixes · 5d67d164
      Joe Perches 提交于
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      5d67d164
  11. 10 10月, 2007 2 次提交
  12. 01 8月, 2007 1 次提交
  13. 10 5月, 2007 1 次提交
  14. 05 5月, 2007 1 次提交
  15. 06 2月, 2007 4 次提交
  16. 08 12月, 2006 1 次提交
  17. 01 10月, 2006 1 次提交
    • J
      [PATCH] Split struct request ->flags into two parts · 4aff5e23
      Jens Axboe 提交于
      Right now ->flags is a bit of a mess: some are request types, and
      others are just modifiers. Clean this up by splitting it into
      ->cmd_type and ->cmd_flags. This allows introduction of generic
      Linux block message types, useful for sending generic Linux commands
      to block devices.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      4aff5e23
  18. 24 8月, 2006 1 次提交
  19. 10 8月, 2006 1 次提交
  20. 12 7月, 2006 1 次提交
  21. 01 7月, 2006 1 次提交
  22. 29 6月, 2006 3 次提交
  23. 28 4月, 2006 1 次提交
  24. 24 3月, 2006 1 次提交
  25. 02 2月, 2006 1 次提交
  26. 07 1月, 2006 2 次提交
  27. 01 5月, 2005 1 次提交