> >> It also seems odd that this name is serving double-duty, as it's > >> alternately either provided by the consumer of the client API or set by > >> mac_client_open() to something that may be of interest to the consumer > >> (such as the associated datalink). One alternative would be to have the > >> name always identify the consumer (mci_client_user or whatever) and have > >> mci_name always identify the associated datalink, and internally use the > >> concatenation of mci_client_user and mci_name name the various related > >> objects like kstats and flows. > >> > > > > sounds like this could work. > > +1
Filed 6872170. -- meem
