1. 13 Jan, 2005 4 commits
    • Paul Mackerras's avatar
      [PATCH] PPC64 Call preempt_schedule on exception exit · f4d0d3c5
      Paul Mackerras authored
      This patch mirrors the recent changes on x86 to call preempt_schedule
      rather than schedule in the exception exit path, in the case where the
      preempt_count is zero and the TIF_NEED_RESCHED bit is set.
      
      I'm a little concerned that this means that we have a window where
      interrupts are enabled and we are on our way into preempt_schedule,
      but preempt_count is still zero.  Ingo's proposed preempt_schedule_irq
      would fix this, and I think something like that should go in.
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      f4d0d3c5
    • Paul Mackerras's avatar
      [PATCH] PPC64 Disable preemption in flush_tlb_pending · ec72859c
      Paul Mackerras authored
      The preempt debug stuff found a place where we were using
      smp_processor_id() without having preemption disabled, in
      flush_tlb_pending.  This patch fixes it by using get_cpu_var and
      put_cpu_var instead of the __get_cpu_var variant.
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ec72859c
    • Jens Axboe's avatar
      [PATCH] possible rq starvation on oom · 80ce63d3
      Jens Axboe authored
      I stumbled across this the other day. The block layer only uses a single
      memory pool for request allocation, so it's very possible for eg writes
      to have allocated them all at any point in time. If that is the case and
      the machine is low on memory, a reader attempting to allocate a request
      and failing in blk_alloc_request() can get stuck for a long time since
      no one is there to wake it up.
      
      The solution is either to add the extra mempool so both reads and writes
      have one, or attempt to handle the situation. I chose the latter, to
      save the extra memory required for the additional mempool with
      BLKDEV_MIN_RQ statically allocated requests per-queue.
      
      If a read allocation fails and we have no readers in flight for this
      queue, mark us rq-starved so that the next write being freed will wake
      up the sleeping reader(s). Same situation would happen for writes as
      well of course, it's just a lot more unlikely.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      80ce63d3
    • Jens Axboe's avatar
      [PATCH] Don't enable ata over eth by default · 6ddb58de
      Jens Axboe authored
      "ATA over Ethernet support" should not default to 'm', it doesn't make
      any sense for a special case driver to do so.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      6ddb58de
  2. 12 Jan, 2005 36 commits