1. 07 7月, 2009 1 次提交
  2. 26 3月, 2009 1 次提交
  3. 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
  4. 06 2月, 2007 2 次提交
  5. 01 7月, 2006 1 次提交
  6. 29 6月, 2006 1 次提交
  7. 01 4月, 2006 1 次提交
  8. 02 2月, 2006 1 次提交
  9. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4