On Thu, 2007-07-06 at 15:30 -0700, Kok, Auke wrote: > our rx interrupt/clean can trigger tx cleans, reaching the same code...
I see that - What i am saying is tx_lock never protects that. Am i mistaken? i.e CPU0 entering tx and and CPU1 entering rx interupt/clean can not be blocked from each other simply by tp->tx_lock because tp->tx_lock only runs on CPU0. Is it a bug then? cheers, jamal - 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
