On 01/07/15 at 05:18pm, Jesse Gross wrote: > On Wed, Jan 7, 2015 at 3:01 PM, Thomas Graf <tg...@suug.ch> wrote: > > The encoding will be based on struct ovs_vxlan_opts which is extended > > as needed by appending new members to the end of the struct. Parsers > > will look at the provided length to see which fields are provided. > > But this means that if there are two extensions that are conflicting > or if one is retired you still need to carry the earlier members of > the struct. Why not make them real netlink attributes?
I figured that due to the limited space available in the VXLAN header the structure would never grow big. I have no problem converting this to use Netlink attributes internally though. Will address this in v2. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
