In the current ON gate, the vnic_notify_walker() function updates va_txinfo under the global vnic_mac_lock mutex.
However, the users of va_txinfo (such as vnic_active_tx) appear to reference va_txinfo without holding any locks, as best I can tell. If the readers aren't synchronized with the writers, then what makes sure that va_txinfo isn't written in the middle of transmitting a packet? Am I missing some other synchronization mechanism? What happens if the underlying NIC is (say) switching between promiscuous and non-promiscuous mode frequently? (Is there a design document that covers how this is supposed to work? I searched, but didn't find anything.) -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
