On Fri, Jul 24, 2015 at 04:16:03PM +0530, Saloni Jain wrote: > As per the Openflow Specification-1.4, Section: 7.4.3.1 Modify Flow Table > Message, Page:73,74: > "When the remaining space in the flow table increases to more than > vacancy_up, and if vacancy up events are enabled, a vacancy up event must be > generated to the controller using the OFPT_TABLE_STATUS message type with > reason OFPTR_VACANCY_UP." > > "When vacancy events are enabled on the table using the OFPTC_VACANCY_EVENTS > flag, either the vacancy up or vacancy down event is enabled. When enabling > events, if the current vacancy is less than vacancy_up, vacancy up events > must be enabled, and vacancy down events must be disabled. When enabling > events, if the current vacancy is greater or equal to vacancy_up, vacancy > down events must be enabled, and vacancy up events must be disabled. When > vacancy events are disabled on the table using the OFPTC_VACANCY_EVENTS flag, > both vacancy up and vacancy down events must be disabled." > > From the above statements, "current vacancy" can be interpreted as occupancy > of the flow table [(no. of. flows/max flows)*100] and not as remaining space > of the table. As per my understanding current vacancy should denote the > remaining/free space of the table.
Can you be more specific about why you think there is a problem? After reading and re-reading this section of the specification a few times, I don't see the issue. Thanks, Ben. _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
