[EMAIL PROTECTED] <[EMAIL PROTECTED]> : [...] > I notice that the vendor-supplied driver doesn't have these bugs.
The M in POMS stands for "my". [...] > Would you be interested in some cleanup patches ? Yes. > In particular, I think I can get rid of tx->lock entirely, or at least > take it off the fast path. All it's protecting is the write to > sp->tx_current, and a few judicious memory barriers can deal with that. I have done a kind of memory barrier trick for the r8169 in the past but it is not clear that I would do it again. Today I would argue more strongly in direction of similar locking amongst different drivers. The tg3 driver is a good model imho. Anyway you have been here for some time so I see no reason to kill any different/new locking scheme you could come with. Off until sunday. -- Ueimor -- 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
