On Fri, Jun 09, 2006 at 04:29:13PM +0100, Daniel Drake wrote: > > Can I interpret your response as: If the TX queue is disabled in > advance, no hard_start_xmit functions will be running on any CPU after > synchronize_net() has returned?
Correct. All callers of hard_start_xmit do so under RCU or equivalent locks so they must be complete by the time synchronize_net() returns. What you got watch out for though are paths where the driver might reenable the queue. That could be a real bug. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - 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
