1. 19 3月, 2006 14 次提交
  2. 28 2月, 2006 1 次提交
    • J
      [PATCH] cfq-iosched: slice expiry fixups · 7b14e3b5
      Jens Axboe 提交于
      During testing of SLES10, we encountered a hang in the CFQ io scheduler.
      Turns out the deferred slice expiry logic is buggy, so remove that for
      now.  We could be left with an idle queue that would never wake up.  So
      kill that logic, always expire immediately.  Also fix a potential timer
      race condition.
      
      Patch looks bigger than it is, because it moves a function.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      7b14e3b5
  3. 06 1月, 2006 1 次提交
  4. 19 11月, 2005 1 次提交
  5. 12 11月, 2005 2 次提交
  6. 04 11月, 2005 1 次提交
  7. 31 10月, 2005 2 次提交
  8. 28 10月, 2005 3 次提交
  9. 11 9月, 2005 1 次提交
  10. 08 9月, 2005 1 次提交
    • B
      [PATCH] block: CFQ refcounting fix · 38f18527
      Brian King 提交于
      I ran across a memory leak related to the cfq scheduler. The cfq
      init function increments the refcnt of the associated request_queue.
      
      This refcount gets decremented in cfq's exit function. Since blk_cleanup_queue
      only calls the elevator exit function when its refcnt goes to zero, the
      request_q never gets cleaned up. It didn't look like other io schedulers were
      incrementing this refcnt, so I removed the refcnt increment and it fixed the
      memory leak for me.
      
      To reproduce the problem, simply use cfq and use the scsi_host scan sysfs
      attribute to scan "- - -" repeatedly on a scsi host and watch the memory
      vanish.
      Signed-off-by: NBrian King <brking@us.ibm.com>
      Acked-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      38f18527
  11. 25 8月, 2005 1 次提交
    • J
      [PATCH] cfq-iosched.c: minor fixes · 9c2c38a1
      Jens Axboe 提交于
      One critical fix and two minor fixes for 2.6.13-rc7:
      
      - Max depth must currently be 2 to allow barriers to function on SCSI
      - Prefer sync request over async in choosing the next request
      - Never allow async request to preempt or disturb the "anticipation" for
        a single cfq process context. This is as-designed, the code right now
        is buggy in that area.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9c2c38a1
  12. 03 8月, 2005 1 次提交
  13. 28 6月, 2005 5 次提交
    • A
      [PATCH] cfq build fix · 99f95e52
      Andrew Morton 提交于
      drivers/block/cfq-iosched.c: In function 'cfq_put_queue':
      drivers/block/cfq-iosched.c:303: sorry, unimplemented: inlining failed in call to 'cfq_pending_requests': function body not available
      drivers/block/cfq-iosched.c:1080: sorry, unimplemented: called from here
      drivers/block/cfq-iosched.c: In function '__cfq_may_queue':
      drivers/block/cfq-iosched.c:1955: warning: the address of 'cfq_cfqq_must_alloc_slice', will always evaluate as 'true'
      make[1]: *** [drivers/block/cfq-iosched.o] Error 1
      make: *** [drivers/block/cfq-iosched.o] Error 2
      
      Cc: Jeff Garzik <jgarzik@pobox.com>
      Cc: Jens Axboe <axboe@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      99f95e52
    • J
      [PATCH] CFQ io scheduler: scheduler switch oops · 96c51ce9
      Jens Axboe 提交于
      If cfq is managing a queue and a new scheduler is later selected, it is
      possible for the cfqd unplug_work work to be queued after the kblockd
      work struct has been flushed.  The problem is the ordering of
      cfq_shutdown_timer_wq() and blk_put_queue() in cfq_put_cfqd().  The
      latter may rearm the work, leaving cfq_kick_queue() with dead data.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      96c51ce9
    • J
      [PATCH] CFQ io scheduler updates · 3b18152c
      Jens Axboe 提交于
      - Adjust slice values
      
      - Instead of one async queue, one is defined per priority level. This
        prevents kernel threads (such as reiserfs/x and others) that run at
        higher io priority from conflicting with others. Previously, it was a
        coin toss what io prio the async queue got, it was defined by who
        first set up the queue.
      
      - Let a time slice only begin, when the previous slice is completely
        done. Previously we could be somewhat unfair to a new sync slice, if
        the previous slice was async and had several ios queued. This might
        need a little tweaking if throughput suffers a little due to this,
        allowing perhaps an overlap of a single request or so.
      
      - Optimize the calling of kblockd_schedule_work() by doing it only when
        it is strictly necessary (no requests in driver and work left to do).
      
      - Correct sync vs async logic. A 'normal' process can be purely async as
        well, and a flusher can be purely sync as well. Sync or async is now a
        property of the class defined and requests pending. Previously writers
        could be considered sync, when they were really async.
      
      - Get rid of the bit fields in cfqq and crq, use flags instead.
      
      - Various other cleanups and fixes
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3b18152c
    • J
      [PATCH] Fix cfq_find_next_crq() · 3d25f356
      Jens Axboe 提交于
      In cfq_find_next_crq(), cfq tries to find the next request by choosing
      one of two requests before and after the current one.  Currently, when
      choosing the next request, if there's no next request, the next
      candidate is NULL, resulting in selection of the previous request.  This
      results in weird scheduling.  Once we reach the end, we always seek
      backward.
      
      The correct behavior is using the first request as the next candidate.
      cfq_choose_req() already has logics for handling wrapped requests.
      Signed-off-by: NTejun Heo <htejun@gmail.com>
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3d25f356
    • J
      [PATCH] Update cfq io scheduler to time sliced design · 22e2c507
      Jens Axboe 提交于
      This updates the CFQ io scheduler to the new time sliced design (cfq
      v3).  It provides full process fairness, while giving excellent
      aggregate system throughput even for many competing processes.  It
      supports io priorities, either inherited from the cpu nice value or set
      directly with the ioprio_get/set syscalls.  The latter closely mimic
      set/getpriority.
      
      This import is based on my latest from -mm.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      22e2c507
  14. 21 6月, 2005 1 次提交
  15. 17 6月, 2005 1 次提交
    • K
      When cfq I/O scheduler is selected, get_request() in __make_request() calls · db3b5848
      Kiyoshi Ueda 提交于
      __cfq_get_queue().  __cfq_get_queue() finds an existing queue (struct
      cfq_queue) of the current process for the device and returns it.  If it's not
      found, __cfq_get_queue() creates and returns a new one if __cfq_get_queue() is
      called with __GFP_WAIT flag, or __cfq_get_queue() returns NULL (this means that
      get_request() fails) if no __GFP_WAIT flag.
      
      On the other hand, in __make_request(), get_request() is called without
      __GFP_WAIT flag at the first time.  Thus, the get_request() fails when there is
      no existing queue, typically when it's called for the first I/O request of the
      process to the device.
      
      Though it will be followed by get_request_wait() for general case,
      __make_request() will just end the I/O with an error (EWOULDBLOCK) when the
      request was for read-ahead.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NKiyoshi Ueda <k-ueda@ct.jp.nec.com>
      Signed-off-by: NJun'ichi Nomura <j-nomura@ce.jp.nec.com>
      db3b5848
  16. 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