Re: [PATCH] async: fix __lowest_in_progress()

2013-01-17 Thread Tejun Heo
Hello, On Thu, Jan 17, 2013 at 10:16:50AM -0800, Linus Torvalds wrote: > Tejun, mind explaining this one a bit more to me? > > If ordering matters, and we have a running queue and a pending queue, > how could the pending queue *ever* be lower than the running one? So, before being converted to w

Re: [PATCH] async: fix __lowest_in_progress()

2013-01-17 Thread Linus Torvalds
Tejun, mind explaining this one a bit more to me? If ordering matters, and we have a running queue and a pending queue, how could the pending queue *ever* be lower than the running one? That implies that something was taken off the pending queue and put on the running queue out of order, right?

[PATCH] async: fix __lowest_in_progress()

2013-01-16 Thread Tejun Heo
083b804c4d3e1e3d0eace56bdbc0f674946d2847 ("async: use workqueue for worker pool") made it possible that async jobs are moved from pending to running out-of-order. While pending async jobs will be queued and dispatched for execution in the same order, nothing guarantees they'll enter "1) move self