On Wed, Sep 11, 2013 at 02:19:02PM +0200, Martino Fornasa wrote: > Ben Pfaff wrote: > >On Tue, Sep 10, 2013 at 05:34:28PM +0200, Martino Fornasa wrote: > >>Ben Pfaff wrote: > >>>On Tue, Sep 10, 2013 at 03:26:48PM +0200, Martino Fornasa wrote: > >>>This sounds very nice. Do you plan to make the result available to > >>>the Open vSwitch community? > >>We do, as soon as we reach a decent stage in the porting. > >> > >>In this moment we are dealing with stp-related components in > >>ofproto-dpif / ofproto-dpifx-xlate ... It seems the trickiest part. > >>In the next days I will have some question to ask... > > > >Yes, this makes sense. Please feel free to ask any questions. > > First question. > I don't really grasp the basic functionalities provided in > ofproto/ofproto-dpif-xlate.c, as it seems that they are involved in > stp. > Could someone clarify that to me? (Or point to the relevant > documentation, of course).
ofproto-dpif-xlate translates a set of OpenFlow actions obtained from the OpenFlow flow table into actions that the kernel (or other datapath) knows how to execute. ofproto-dpif-xlate is involved in STP in two ways. First, this code detects when STP BDPUs pass through the switch and passes them to the stp module for handling. Second, this code drops output actions that forward packets to ports that STP has disabled. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
