> But the door name is not exposed to administrators anyway, so that it does > not need to have semantic meaning.
It's not directly exposed, but they will see it through pfiles(1) and in the filesystem itself. So I'd prefer for it to be meaningful. > Further, using link name as the door name only introduces unnecessary > complication. The door name is derived in the attach() routine and kept in > the kernel, although it can be done to update the door name every time the > link name is changed, I don't see why that is necessary. Then maybe it could just use the device name? Or does that make things complex somewhere else? > > > b. Change the wpa to get the linkid of a specific wireless link and > > store > > > that linkid locally. Therefore, it does not need to do > > linkname-to-linkid > > > mapping all the time to do other operations like scan(), setkey() etc. > > > > As above, I don't yet understand why the linkid needs to be used here. > > Because it will call into libdladm functions will take linkid as the > argument. OK. -- meem
