On Tue, Dec 01, 2015 at 12:51:11PM +0530, saloni.jai...@gmail.com wrote:
> From: Saloni Jain <saloni.j...@tcs.com>
>
> On change in a table state, the controller needs to be informed with
> the OFPT_TABLE_STATUS message. The message is sent with reason
> OFPTR_VACANCY_DOWN or OFPTR_VACANCY_UP in case of change in remaining
> space eventually crossing any one of the threshold.
>
> Signed-off-by: Saloni Jain <saloni.j...@tcs.com>
> Co-authored-by: Rishi Bamba <rishi.ba...@tcs.com>
> Signed-off-by: Rishi Bamba <rishi.ba...@tcs.com>
> ---
> Difference between v5 <-> v6
> - Done changes in code so that TABLE_STATUS message will be sent
> only when it croses the mentioned threshold.
> - Rebase with latest master
I don't see anything that disables the event once it crosses a
threshold, so I think that this will still send a table status message
every time the flow table changes and the occupancy is past one
threshold or another.
The spec says:
When the remaining space in the flow table decreases to less than
vacancy_down, and if vacancy down events are enabled, a vacancy down
event must be generated to the controller using the OFPT_TABLE_STATUS
message type with reason OFPTR_VACANCY_DOWN (see 7.4.5). Further vacancy
down events are disabled until a vacancy up event is generated.
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. Further vacancy up events are
disabled until a vacancy down event is generated.
That is, sending an event disables any further events of that type until
the opposite event is sent.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
