[ovs-dev,2/3] upcall: Change should_revalidate to use max-revalidator value
diff mbox series

Message ID 1563698063-28256-3-git-send-email-roid@mellanox.com
State New
Headers show
Series
  • be able to tune revalidator timing
Related show

Commit Message

Roi Dayan July 21, 2019, 8:34 a.m. UTC
From: Vlad Buslov <vladbu@mellanox.com>

Revalidate if dump duration was longer than half of max-revalidator
timeout, instead of hardcoded 200msec value.

Signed-off-by: Vlad Buslov <vladbu@mellanox.com>
Acked-by: Roi Dayan <roid@mellanox.com>
---
 ofproto/ofproto-dpif-upcall.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch
diff mbox series

diff --git a/ofproto/ofproto-dpif-upcall.c b/ofproto/ofproto-dpif-upcall.c
index b3598742b4d1..00c8e6ddcfaa 100644
--- a/ofproto/ofproto-dpif-upcall.c
+++ b/ofproto/ofproto-dpif-upcall.c
@@ -2040,7 +2040,7 @@  should_revalidate(const struct udpif *udpif, uint64_t packets,
         return true;
     }
 
-    if (udpif->dump_duration < 200) {
+    if (udpif->dump_duration < ofproto_max_revalidator / 2) {
         /* We are likely to handle full revalidation for the flows. */
         return true;
     }