On Apr 4, 2008, at 11:53 AM, James Carlson wrote: > It looks like that's used in lieu of a writer equivalent for > VNIC_MAC_REFHOLD, but I'm still not sure how it works. Holding the > lock stops new reference holds and releases -- is that intentional, or > is the only use for this lock to make sure that the mac_vnic_tx_get() > call and the assignment to va_txinfo are atomic with respect to other > callers of vnic_notify_walker()? > > (I'm beginning to suspect that the latter is the only purpose ...)
It's the latter. Nicolas. -- Nicolas Droux - Solaris Networking - Sun Microsystems, Inc. [EMAIL PROTECTED] - http://blogs.sun.com/droux _______________________________________________ networking-discuss mailing list [email protected]
