commit 8acd4ead47d98e3f91f35881c20c422330b2044b
Author: Praveen K V <email address hidden>
Date: Fri May 20 23:49:35 2016 +0530
Limit number of entries visited per task for ageing
Problem:
Flow ageing currently fires a timer every 50msec. As the flow-table size
increases, the number of entries to visit per timer also increases. This can
lead to large latencies on firing of a timer. It is desirable to limit the
latency
Solution:
When timer is fired, ageing algorithm compute number of entries to visit.
Instead of scanning flow table in context of timer, it starts a task and
visits 256 entries for every run of task. Task continuation is used if there
are more entries pending on completion of task.
Reviewed: https:/ /review. opencontrail. org/20976 github. org/Juniper/ contrail- controller/ commit/ 8acd4ead47d98e3 f91f35881c20c42 2330b2044b
Committed: http://
Submitter: Zuul
Branch: master
commit 8acd4ead47d98e3 f91f35881c20c42 2330b2044b
Author: Praveen K V <email address hidden>
Date: Fri May 20 23:49:35 2016 +0530
Limit number of entries visited per task for ageing
Problem:
Flow ageing currently fires a timer every 50msec. As the flow-table size
increases, the number of entries to visit per timer also increases. This can
lead to large latencies on firing of a timer. It is desirable to limit the
latency
Solution:
When timer is fired, ageing algorithm compute number of entries to visit.
Instead of scanning flow table in context of timer, it starts a task and
visits 256 entries for every run of task. Task continuation is used if there
are more entries pending on completion of task.
Change-Id: Icb10bec94d2923 442c453c2b4071e a7ab4d9d702
Partial-Bug: #1568126
Partial-Bug: #1572270
Partial-Bug: #1572471