On Mon, Jan 29, 2018 at 11:52:34AM +0800, Jianfeng Tan wrote: > >On Sun, Jan 28, 2018 at 11:39:29PM +0800, Jianfeng Tan wrote: > >> Hi, > >> > >> In the openflow, we set no-flood PodMod operation through openflow 1.0; > for > >> later openflow versions, no-flood is dropped. > >> We can refer to below two macro definitions. > >> > >> #define OFPPC10_ALL (OFPPC_PORT_DOWN | OFPPC10_NO_STP | > OFPPC_NO_RECV | > >> \ > >> OFPPC10_NO_RECV_STP | OFPPC10_NO_FLOOD | > >> OFPPC_NO_FWD | \ > >> OFPPC_NO_PACKET_IN) > >> > >> #define OFPPC11_ALL \ > >> (OFPPC_PORT_DOWN | OFPPC_NO_RECV | OFPPC_NO_FWD | > >> OFPPC_NO_PACKET_IN) > >> > >> Would like to know why no-flood is not one of the common flags? Or do we > >> have any other BKM to supersede such port config? > > > >The OpenFlow 1.1 and later specifications don't have a "no flood" bit. > > Thank you for the reply. > > We also notice that it's the OpenFlow protocol (later version) does not > support > this bit. But we wonder why it's removed from the protocol? It's useless? Or > we have an alternative to cover this.
I wasn't involved in the standardization of OpenFlow 1.1, but I'd guess that groups were intended to replace this feature. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
