> So this is really just like synchronize_irq()? Using msleep is bogus > because you want to spin, you are only waiting for a softirq on the other > cpu to finish. If you wait for a whole millisecond and sleep that > is far longer than the napi routine should take. > > You could even optimize it like synchronize_irq() for the non-SMP case.
It's just like synchronize_irq() indeed. I used the mlseep() just like napi_disable() mostly because I use it in a very similar context, for disabling my sub-channels on things like link change etc... where I need to reconfigure parts of the chip. I prefer sleeping in my case but I agree that if somebody else was going to use for something else more performance critical, it might be an issue. On the other hand, spinning will not be nice for my usage scenario :-) I agree about the SMP optimisation though again, in my usage pattern, it's very unimportant (similar code path as napi_disable) I'll respin later today though. Cheers, Ben. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
