Differences

This shows you the differences between two versions of the page.

--- 0x13:reports:d1t3t04-an-asynchronous-dataplane-for-frr [2019/04/03 21:35] – ehalep
+++ 0x13:reports:d1t3t04-an-asynchronous-dataplane-for-frr [2019/09/28 17:04] (current) – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 Report by: Donald Sharp
-This session followed the previous workshop of FRR and discussed an asynchronous data-plane / zebra.
+This session was a follow-up from the previous FRR workshop and discussed the asynchronous data-plane / zebra.
-voltanet.io presenter, not the coder himself though.
+The presenter was from voltanet.io, however it was not the coder himself.
-- ZAPI - API between zebra and routing daemons.
+The talk begun with the ZAPI - API between zebra and routing daemons. Now it has one thread per client in ZEBRA. This was followed by asynchronous communication with FIB. E.g.: remote switch (voltanet). There are two threads now: zebra-main, zebra-dplane connected by two queues. The zebra dataplane talks with "kernel". The ACK path (installed in HW) is only used by sharpd (installs 1 million routes, testing daemon), but needed for BGP, RIP according to Donald.
-  Now one thread per client in ZEBRA.
-- Aynchronuous communication with FIB. E.g.: remote switch (voltanet).
-  two threads now: zebra-main, zebra-dplane connected by two queues.
-  zbra dplane talks with "kernel".
-- ACK path (installed in HW): only used by sharpd (installs 1 million
-  routes,
-  testing daemon), but needed for BGP, RIP according to donald.
-  cumulus linux: currently no feedback from linux-kernel when route is
-  installed onto ASIC (eg: broadcom).
-- kiran: could expand dplane daemon to directly use chip API to install
-  routes, not relying on linux-kernel driver doing it. A: Yes.
-- toerless: change nexthop-group-members ? Donald: No, not there yet.
-Site: https://www.netdevconf.org/0x13/session.html?talk-FRR-async
-Slides:
-Videos:
+A comment from cumulus linux, there is currently no feedback from linux-kernel when route is installed onto ASIC (eg: broadcom).
+Kiran asked whether the dataplane deamon could expand to directly use chip API to install routes, not relying on linux-kernel driver doing it.
+The answer was yes.
+Toerless then asked to change nexthop-group-members?
+Donald replied that it's not there yet.
+Site: https://www.netdevconf.info/0x13/session.html?talk-FRR-async