commit eb7e5a11b3334d1d58ca8b0cd8103a31d6b49bea
Author: Praveen K V <email address hidden>
Date: Fri Apr 29 15:58:11 2016 +0530
Unify flow-update handling
The current code handles flow-update resulting from add/change for
DBEntries (interface, acl, vn, nh) as different cases. However, there is
only a minor difference between handling based on different DBEntries.
This commit unifies the code to handle DBEntry add/change into two
cases,
- Flows need re-valuation. This is case where we only do
policy-lookup and identify new actions
- Flows needing re-computation. This is case where there is route
change and flow need complete re-valuation due to add/delete of
routes
Additionally, two flags are added in flow to ensure state-compression.
Reviewed: https:/ /review. opencontrail. org/20226 github. org/Juniper/ contrail- controller/ commit/ eb7e5a11b3334d1 d58ca8b0cd8103a 31d6b49bea
Committed: http://
Submitter: Zuul
Branch: master
commit eb7e5a11b3334d1 d58ca8b0cd8103a 31d6b49bea
Author: Praveen K V <email address hidden>
Date: Fri Apr 29 15:58:11 2016 +0530
Unify flow-update handling
The current code handles flow-update resulting from add/change for
DBEntries (interface, acl, vn, nh) as different cases. However, there is
only a minor difference between handling based on different DBEntries.
This commit unifies the code to handle DBEntry add/change into two
cases,
- Flows need re-valuation. This is case where we only do
policy-lookup and identify new actions
- Flows needing re-computation. This is case where there is route
change and flow need complete re-valuation due to add/delete of
routes
Additionally, two flags are added in flow to ensure state-compression.
Conflicts: agent/pkt/ flow_entry. cc
src/vnsw/
Change-Id: Ifeb696d2ab651f 656fbafd45e5e66 a52adb65ade
Partial-Bug: #1568126
Partial-Bug: #1572270
Partial-Bug: #1572471