Hi, I'm going to eventually nuke OACTIVE. It just doesn't hold any meaning nowdays.
Having OACTIVE serialised behind the iflock doesn't actuallly help as much as it used to - because there's multiple concurrent TX path entry points, it's very possible that OACTIVE will get set in one TXing thread during the _middle_ of the execution of another TX thread. That's why you need some kind of higher level serialisation or locking around the TX path to have it make any sense. -adrian _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
