>> a. It is needed to have this link created (specifically, the >> dls_vlan_t created), so that that structure can keep the zoneid >> information. >> This information is then used by dladm to lookup the zoneid of a link, >> when one tries to use dladm to change or get the zoneid of a link.
> Yes, get it created (if it is not already there) is one purpose, furthermore, > it is more important to "hold" the link on behalf of the zone, note that > the zone could just "own" the datalink and not using it at all, thus we hold > a reference to keep the dls_vlan_t alive. > That is the same as my understanding. I forgot to mention that one goal of DLDIOCHOLDVLAN instead of just openning that link, is to "open" the link but without mark it as "opened", so that dladm can assign it to another zone. >> As part of vanity naming, we could do an implied "dladm create- >> vlan" as part of exclusive-zone boot, and that VLAN's devfs minor node will >> be >> created then, therefore requirement (b) is no longer needed. > What is the "implied dladm create-vlan"? doesn't it require some similar > operations? > I mean to a equivalent "dladm create-vlan" operation as part of the zone boot process. But I saw Erik's concern, I will reply there. Thanks - Cathy
