On Sep 30, 2014, at 9:16 AM, Samuel Ghinet <sghi...@cloudbasesolutions.com> wrote:
> Nithin, > > basically, any userspace code that used flows was commented out. And code > that was trying to set qos to the netdev was commented out (because it was > retrying forever). > And netlink functions that used rtnetlink (were used for qos and netdev, if I > am not mistaken) were commented out, so they do not get called. > > So in principle, the functions in userspace that call into the kernel to add > port, set port and delete port were reached, and thus were tested. > I used only one bridge (in patch 00 I explained about problems with multiple > bridges / multiple internal ports) - basically, I used only one, because > otherwise it periodically re-tries the creation of the failed internal vport. > I added manually the VM ports (used the WMI script as well). The "internal" > port is created automatically by the userspace. > I had tested the creation and destruction only. I.e. I did not test vxlan > tunneling itself (I think this would be impossible at this stage), only that > the vports are created and destroyed as they should. Sounds good. Thanks Alin and Samuel. I should have the netdev-windows implementation out for review today, and will review your patches too. -- Nithin _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
