> There is a rb tree per cpu. Each time a task is blocked on an IO, it > is inserted into the tree. When the IO is complete and the task is > woken up, its avg latency is updated with the time spent to wait the > IO and it is removed from the tree. The next time, it will be inserted > into the tree again in case of io_schedule.
Is there an assumption built-in here that the device interrupt is targeted at the same CPU as where the task is queued? thanks, Len Brown, Intel Open Source Technology Center -- 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/
