commit a451af4ce4d3c84f788420b7e7d2015508597a65
Author: Praveen K V <email address hidden>
Date: Thu Aug 13 12:11:51 2015 +0530
Run FlowTable processing from work-queue
This change is a step towards running Flow setup in multiple threads. Flow
creation is a two step process,
FlowHandler :
FlowEntry are created and flow action are determined in this context.
This stage can potentially run in multiple threads (future commits)
FlowHandler runs from a workqueue in "Agent::FlowHandler" task context
FlowTable :
1. Manage flow_entry_map_ which contains all flows
2. Enforce the per-VM flow limits
3. Generate events to KSync and FlowMgmt modueles
FlowTable runs from a workqueue in "Agent::FlowTable" task context
Reviewed: https:/ /review. opencontrail. org/13030 github. org/Juniper/ contrail- controller/ commit/ a451af4ce4d3c84 f788420b7e7d201 5508597a65
Committed: http://
Submitter: Zuul
Branch: R2.22-dev
commit a451af4ce4d3c84 f788420b7e7d201 5508597a65
Author: Praveen K V <email address hidden>
Date: Thu Aug 13 12:11:51 2015 +0530
Run FlowTable processing from work-queue
This change is a step towards running Flow setup in multiple threads. Flow
creation is a two step process,
FlowHandler : :FlowHandler" task context
FlowEntry are created and flow action are determined in this context.
This stage can potentially run in multiple threads (future commits)
FlowHandler runs from a workqueue in "Agent:
FlowTable :
1. Manage flow_entry_map_ which contains all flows
2. Enforce the per-VM flow limits
3. Generate events to KSync and FlowMgmt modueles
FlowTable runs from a workqueue in "Agent::FlowTable" task context
Change-Id: I74c10561c20075 a4fb5a3c2b09c1a 8ddb9a9d599
Partial-Bug: #1479295