@Armando: yep, I'm using ovs with dpdk, and qemu is in Server mode.(i.e. -chardev socket,id=charnet1,path=/var/run/openvswitch/vhu69bc5ac0-a8,server).
I don't understand why ovs should keep the metadata(bridge_name, trunk_id, supborts) in externals_ids. This metadata is already stored in ovs. We can easy get bridge name for parent port using "ovs-vsctl port-to-br" command, then we can receive all bridge ports using "ovs-vsctl list-ports", from this list we can easy restore patch ports on integration bridge. Could you please clarify why we need to duplicate the info in ovs db? For performance reason?
@Armando: yep, I'm using ovs with dpdk, and qemu is in Server mode.(i.e. -chardev socket, id=charnet1, path=/var/ run/openvswitch /vhu69bc5ac0- a8,server) .
I don't understand why ovs should keep the metadata( bridge_ name, trunk_id, supborts) in externals_ids. This metadata is already stored in ovs. We can easy get bridge name for parent port using "ovs-vsctl port-to-br" command, then we can receive all bridge ports using "ovs-vsctl list-ports", from this list we can easy restore patch ports on integration bridge. Could you please clarify why we need to duplicate the info in ovs db? For performance reason?