On Fri, May 31, 2013 at 12:52 PM, Eugene Istomin <e.isto...@edss.ee> wrote: > Hello, > > > > i'm trying to understand Xen/OVS - VLAN offloading > > > > > > In my testbed: > > > > #ovs-vsctl show > > Bridge vlannet > > Port "vif5.0" > > tag: 1002 > > Interface "vif5.0" > > Port vlannet-bond > > Interface "vlannet2" > > Interface "vlannet1" > > Port vlannet > > Interface vlannet > > type: internal > > Port "vif3.0" > > tag: 1002 > > Interface "vif3.0" > > ovs_version: "1.10.0" > > > > 1) Xen Dom0 HW interface -> > > ethtool -k vlannet1 > > > > .. > > rx-vlan-offload: on > > tx-vlan-offload: on > > rx-vlan-filter: on [fixed] > > .. > > > > 2) OVS system interface -> > > ethtool -k ovs-system > > > > .. > > rx-vlan-offload: off [fixed] > > tx-vlan-offload: on > > rx-vlan-filter: off [fixed] > > .. > > > > 3) DomU netback interface -> > > ethtool -k ovs-system > > > > .. > > rx-vlan-offload: off [fixed] > > tx-vlan-offload: off [fixed] > > rx-vlan-filter: off [fixed] > > > > .. > > > > > > As i see, VLAN offloading is partially implemented in OVS and didn't > implemented in Xen means VLAN tagged traffic inside VM will make additional > latency. > > > > Can anyone have info about OVS->VM VLAN offloading configuration?
This is dependent on the hypervisor and not being restricted by OVS. However, the direct benefits of vlan offloading are very minimal and are really only useful in relation to enabling other offloads. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
