Routing tables now have their own loops.

This basically means that:
* there are some more levels of indirection and asynchronicity, mostly
  in cleanup procedures, requiring correct lock ordering
* all the internal table operations (prune, next hop update) are done
  without blocking the other parts of BIRD
* the protocols may get their own loops very soon

1 files changed, 8 insertions, 4 deletions

diff --git a/proto/static/static.c b/proto/static/static.c
index 45791e8e..bd7f3f5b 100644
--- a/proto/static/static.c
+++ b/proto/static/static.c
@@ -491,10 +491,12 @@ static_start(struct proto *P)
     static_lp = lp_new(&root_pool, LP_GOOD_SIZE(1024));
 
   if (p->igp_table_ip4)
-    rt_lock_table(p->igp_table_ip4);
+    RT_LOCKED(p->igp_table_ip4, t)
+      rt_lock_table(t);
 
   if (p->igp_table_ip6)
-    rt_lock_table(p->igp_table_ip6);
+    RT_LOCKED(p->igp_table_ip6, t)
+      rt_lock_table(t);
 
   p->event = ev_new_init(p->p.pool, static_announce_marked, p);
 
@@ -521,10 +523,12 @@ static_shutdown(struct proto *P)
     static_reset_rte(p, r);
 
   if (p->igp_table_ip4)
-    rt_unlock_table(p->igp_table_ip4);
+    RT_LOCKED(p->igp_table_ip4, t)
+      rt_unlock_table(t);
 
   if (p->igp_table_ip6)
-    rt_unlock_table(p->igp_table_ip6);
+    RT_LOCKED(p->igp_table_ip6, t)
+      rt_unlock_table(t);
 
   return PS_DOWN;
 }