Differences

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

--- 0x13:reports:d1t3t04-an-asynchronous-dataplane-for-frr [2019/04/03 21:53] – 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.
 The presenter was from voltanet.io, however it was not the coder himself.
-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 aynchronuous 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.
+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.
 A comment from cumulus linux, there is currently no feedback from linux-kernel when route is installed onto ASIC (eg: broadcom).
@@ Line 15: / Line 15: @@
 Donald replied that it's not there yet.
-Site: https://www.netdevconf.org/0x13/session.html?talk-FRR-async
+Site: https://www.netdevconf.info/0x13/session.html?talk-FRR-async
-Slides:
-Videos: