> When I have to go back to this I'd expect to have the VNIC code > expose the true details of the underlying link.
OK, that sounds good. > As others indicated, any code that directly opens mac devices (by > calling mac_open()) is likely to need support for cook/uncook > operations. Right now that's a set something like dls, vsw, aggr, > vnic and xnbo. The code is not complex, but knowing that it's > required is the first step :-) I'm still a bit confused here. Any code that directly opens mac devices already has to prepare itself for opening a non-Ethernet mactype today, so what change is required? -- meem
