1. 16 10月, 2007 2 次提交
  2. 13 10月, 2007 4 次提交
  3. 12 10月, 2007 1 次提交
  4. 10 10月, 2007 17 次提交
  5. 15 9月, 2007 1 次提交
  6. 13 9月, 2007 1 次提交
    • J
      Fix race with shared tag queue maps · f3da54ba
      Jens Axboe 提交于
      There's a race condition in blk_queue_end_tag() for shared tag maps,
      users include stex (promise supertrak thingy) and qla2xxx.  The former
      at least has reported bugs in this area, not sure why we haven't seen
      any for the latter.  It could be because the window is narrow and that
      other conditions in the qla2xxx code hide this.  It's a real bug,
      though, as the stex smp users can attest.
      
      We need to ensure two things - the tag bit clearing needs to happen
      AFTER we cleared the tag pointer, as the tag bit clearing/setting is
      what protects this map.  Secondly, we need to ensure that the visibility
      of the tag pointer and tag bit clear are ordered properly.
      
      [ I removed the SMP barriers - "test_and_clear_bit()" already implies
        all the required barriers.  -- Linus ]
      
      Also see http://bugzilla.kernel.org/show_bug.cgi?id=7842Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f3da54ba
  7. 12 8月, 2007 1 次提交
  8. 31 7月, 2007 1 次提交
  9. 28 7月, 2007 1 次提交
  10. 27 7月, 2007 2 次提交
  11. 24 7月, 2007 3 次提交
  12. 22 7月, 2007 1 次提交
  13. 21 7月, 2007 3 次提交
  14. 20 7月, 2007 2 次提交
    • A
      cfq: Write-only stuff in CFQ data structures · 8350163a
      Alexey Dobriyan 提交于
      There are some leftover bits from the task cooperator patch, that was
      yanked out again. While it will get reintroduced, no point in having
      this write-only stuff in the tree. So yank it.
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      8350163a
    • V
      cfq: async queue allocation per priority · c2dea2d1
      Vasily Tarasov 提交于
      If we have two processes with different ioprio_class, but the same
      ioprio_data, their async requests will fall into the same queue. I guess
      such behavior is not expected, because it's not right to put real-time
      requests and best-effort requests in the same queue.
      
      The attached patch fixes the problem by introducing additional *cfqq
      fields on cfqd, pointing to per-(class,priority) async queues.
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      c2dea2d1