I see. I think one option could be do extra validations depending on the error returned by ofproto_check_ofpacts like checking if previous entries in the bundle would make the validation successful. But since group and meter mods are not implemented yet this isn't feasible. I need to focus on my project for now but later I might be able to help with group and meter mods.
To submit the patch is "just" follow CONTRIBUTING.md, right? Jarno Rajahalme <ja...@ovn.org> escreveu no dia terça, 15/03/2016 às 17:31: > I think I’ll worry about that when I get to adding group and meter support. > > Jarno > > > On Mar 14, 2016, at 8:47 PM, Ben Pfaff <b...@ovn.org> wrote: > > > > Jarno, what do you think? > > > > On Mon, Mar 14, 2016 at 11:16:27PM +0000, André Mantas wrote: > >> Ok. And what about Packet_Out validation complicating the > implementation of > >> group and meter mod in bundles? > >> > >> Should I create new validation functions that don't check for group and > >> meter in the action of Packet_Out? > >> > >> Ben Pfaff <b...@ovn.org> escreveu no dia segunda, 14/03/2016 às 16:54: > >> > >>> On Wed, Mar 09, 2016 at 09:10:41AM +0000, André Mantas wrote: > >>>> By the way, I'm still starting vswitchd with valgrind and detected > some > >>>> memory errors after using "sudo ovs-appctl exit". Is there other way > to > >>>> exit/stop ovs? > >>>> > >>>> To run I used: valgrind --tool=memcheck --leak-check=full ovs-vswitchd > >>>> --pidfile --detach -v --log-file > >>> > >>> These aren't anything to worry about. OVS does a number of one-time > >>> allocations that it doesn't bother to release. Some of them get > >>> released when OVS exits, some of them don't. > >>> > >>> We'd take patches to release them, but it's not an important problem. > >>> > > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
