![]() | |||||||||||||
Messages in this thread |
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 <oleg@tv-sign.ru> Applied, thanks. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-08-29 09:15 [from the cache] ©2003-2008 | |||||||||||||