On Mon, 29 Aug 2011, Ming Lei wrote: > Suppose HC can see the old value in hw_token, which has the ACTIVE bit clear. > > The qtd transaction will not be executed until the new token is > flushed into memory. > From view of CPU, the irq is still be delayed because ioc irq is generated > after the qtd transaction is executed when new token is flushed into > memory. The delay > depends on how long the token will be flushed into memory. That's right. > From my observation, the delay is commonly over 5ms for CSW, sometimes the delay > is more than 20ms, so caused the bad performance. No wonder! Do you see the same sort of performance degradation when using shared memory to communicate between two CPUs? Regardless, this is not quite the same as what you were talking about earlier. You specifically mentioned ... so ehci may fetch a inconsistent qtd and execute it, then mistaken IOC or "total bytes to transfer" are read by EHCI and cause delayed irq or lost irq. Bad performance is different from inconsistencies and lost IRQs. > Also I am not sure if EHCI can read the old hw_token correctly in this kind of > inconsistent memory state. The memory state is NOT inconsistent! It is consistent at all times, both before and after the new hw_token value is stored. The memory state is just slow to update, that's all. This is a speed issue, not a correctness issue. Nevertheless, it remains true that you want to add a memory barrier instruction simply in order to speed up a cache writeback, not to force any sort of ordering. This needs to be explained carefully in the code (not just in the patch description!) and it needs to be done in a way that won't affect other architectures. Also, as you mentioned before, you may want to do the same thing in qh_link_async() just after the head->hw->hw_next = dma; line. Delays in flushing that write would also slow down performance. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
