Re: [PATCH] exit_io_context: don't disable irqs

On Sun, Aug 27 2006, Oleg Nesterov wrote:
> We don't need to disable irqs to clear current->io_context, it is
> protected by ->alloc_lock. Even IF it was possible to submit I/O from
> IRQ on behalf of current this irq_disable() can't help:
> current_io_context() will re-instantiate ->io_context after
> irq_enable().
> 
> We don't need task_lock() or local_irq_disable() to clear ioc->task.
> This can't prevent other CPUs from playing with our io_context anyway.
> 
> Signed-off-by: Oleg Nesterov <[email protected]>

Applied, thanks.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] exit_io_context: don't disable irqs
    • From: Oleg Nesterov <[email protected]>

• Prev by Date: Re: [PATCH RESEND] sys_ioprio_set: don't disable irqs
• Next by Date: [PATCH] unusual device Sony Ericsson M600i
• Previous by thread: [PATCH] exit_io_context: don't disable irqs
• Next by thread: [PATCH RESEND] sys_ioprio_set: don't disable irqs
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]