Cathy Zhou wrote: > It is symmetrical with dls_create() which also take mac_handle_t as the > input.
But in that case, a MAC handle is required in order for dls to make the initial association of the given linkid with a MAC handle. In the case of dls_destroy(), the MAC handle is not technically required, as it is only used to derive a link id, which could have been passed in as a parameter instead. > As dls_create() and dls_destroy() are often called by pseudo link driver > (such as aggr, iptun) to create/destroy data-links after/before > mac_register()/mac_unregister(), my intention is to not require those > drivers to keep the linkid information, but instead create/destroy links > using mac_handle_t which is returned by mac_register(). Okay. It's of little consequence to me, I just thought the parameters were a little out of scope for the interface, and that it was easy enough for the consumers to remember which linkid's they had created. iptun stores the linkid in its instance structure already anyway. -Seb
