On Wed, Dec 30, 2015 at 07:29:15PM -0500, Thomas F Herbert wrote: > > > On 11/9/15 3:58 PM, Ben Pfaff wrote: > >On Fri, Oct 02, 2015 at 05:31:58PM -0400, Thomas F Herbert wrote: > >>From: "Thomas F. Herbert" <[email protected]> > >> > >>ToDo: The flow structure needs to be updated to hold both the inner and > >>outer > >>tpid since these are encoded by the kernel module. > >I think I'd like to see the version with both TPIDs encoded. That's the > >way I've always envisioned this working. > I have been working on the changes to add the inner and outer tpids to the > flow struct this week. I changed flow struct to place two vlan structs right > after the dl_type with the outer first followed by the inner. This is done > so the miniflow would still work with few modifications because dl_type and > outer tci are sequential. However, this raises the issue as to whether the > outer tpid and the inner vlan, tci and tpid should also be added to the > miniflow. What are your thoughts?
I don't understand the question. A miniflow and a flow represent the same data, only a miniflow has a compressed format. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
