On Oct 8, 2014, at 5:21 PM, Alin Serdean <[email protected]> wrote:
> The field nameLink of the OVS_VPORT_ENTRY is the link within the > OVS_SWITCH_CONTEXT's hash array of vports nameHashArray, hashed by the > ovsName field of the OVS_VPORT_ENTRY. > > Later on, the friendly name of the hyper-v switch port will need to be > set from userspace using WMI. This will require that the hyper-v switch > port friendly name be set to the exact string value as the ovs > (datapath) port name set from netlink command vport add. > > The vport will need to differentiate between the ovs (datapath) port > name and hyper-v switch port friendly name, because they may differ in > erroneous scenarios, or state differences between the hyper-v switch > port and the ovs (datapath) port. This may happen if the vport was > created by the netlink command vport add, but the VM disconnected (i.e. > the hyper-v switch port was later deleted). > > Storing another field in vport, "portFriendlyName" would normally > make the current switchContext->nameHashArray and vport->nameLink > confusing since the "name"-s may be understood to mean the hyper-v > switch port friendly name, or the hyper-v switch port name, when it > actually refers to the ovs (datapath) port name. > > Hence, the variable nameHashArray is renamed to ovsPortNameHashArray, > while the nameLink is renamed to ovsPortNameLink. This change will make > a clearer connection between these and the vport field "ovsName" to > which they revolve around. > > Signed-off-by: Samuel Ghinet <[email protected]> > Co-authored-by: Alin Gabriel Serdean <[email protected]> Acked-by: Nithin Raju <[email protected]> Tested-by: Nithin Raju <[email protected]> _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
