1. 07 1月, 2006 12 次提交
  2. 02 1月, 2006 1 次提交
  3. 20 12月, 2005 1 次提交
  4. 16 12月, 2005 1 次提交
    • M
      [SCSI] seperate max_sectors from max_hw_sectors · defd94b7
      Mike Christie 提交于
      - export __blk_put_request and blk_execute_rq_nowait
      needed for async REQ_BLOCK_PC requests
      - seperate max_hw_sectors and max_sectors for block/scsi_ioctl.c and
      SG_IO bio.c helpers per Jens's last comments. Since block/scsi_ioctl.c SG_IO was
      already testing against max_sectors and SCSI-ml was setting max_sectors and
      max_hw_sectors to the same value this does not change any scsi SG_IO behavior. It only
      prepares ll_rw_blk.c, scsi_ioctl.c and bio.c for when SCSI-ml begins to set
      a valid max_hw_sectors for all LLDs. Today if a LLD does not set it
      SCSI-ml sets it to a safe default and some LLDs set it to a artificial low
      value to overcome memory and feedback issues.
      
      Note: Since we now cap max_sectors to BLK_DEF_MAX_SECTORS, which is 1024,
      drivers that used to call blk_queue_max_sectors with a large value of
      max_sectors will now see the fs requests capped to BLK_DEF_MAX_SECTORS.
      Signed-off-by: NMike Christie <michaelc@cs.wisc.edu>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      defd94b7
  5. 13 12月, 2005 2 次提交
  6. 29 11月, 2005 5 次提交
  7. 23 11月, 2005 6 次提交
  8. 18 11月, 2005 2 次提交
    • N
      [PATCH] md: fix is_mddev_idle calculation now that disk/sector accounting... · c0e48521
      NeilBrown 提交于
      [PATCH] md: fix is_mddev_idle calculation now that disk/sector accounting happens when request completes
      
      md needs to monitor the rate of requests to its devices when doing
      resync/recovery so that it can back-off when there is non-resync IO.  It
      does this by comparing resync IO, which it counts, with total IO which is
      taken from disk_stats.
      
      disk_stats were recently changed to account sectors when a request
      completes instead of when it is queued.  This upsets md's calculations.
      
      We could do the sync_io accounting at the end of requests too, but that has
      problems.  If an underlying device is an md array, the accounting will
      still be done when the request is submitted.  This could be changed for
      some raid levels, but it cannot be changed for raid0 or linear without
      substantial code changes.
      
      So instead, we increase the error that is_mddev_idle allows, up to the
      maximum amount of resync IO that can be in flight at any time.  The
      calculation is current fragile as each personality as different limits for
      in-flight resync.  This should be fixed up.
      
      For now, this simple patch fixes the problem.
      
      Increasing the error margin decreases the sensitivity to non-resync IO.  To
      partially compensate for this, the time to wait when non-resync IO is
      detected is increased so that less steady IO is required to keep the resync
      at bay.
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      c0e48521
    • N
      [PATCH] md: don't pass a NULL file* into ->prepare_write() · 34ef75f0
      Neil Brown 提交于
      Some filesystems go oops.
      Signed-off-by: NNeil Brown <neilb@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      34ef75f0
  9. 16 11月, 2005 2 次提交
  10. 09 11月, 2005 8 次提交