Differences

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

--- 0x13:reports:d1t3t04-an-asynchronous-dataplane-for-frr [2019/03/27 22:47] – created ehalep
+++ 0x13:reports:d1t3t04-an-asynchronous-dataplane-for-frr [2019/09/28 17:04] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 Talk – Nuts-n-Bolts: An Asynchronous Dataplane for FRR
 Speakers: Mark Stapp
-Report by:
+Report by: Donald Sharp
+This session was a follow-up from the previous FRR workshop and discussed the asynchronous data-plane / zebra.
-Site: https://www.netdevconf.org/0x13/session.html?talk-FRR-async
+The presenter was from voltanet.io, however it was not the coder himself.
-Slides:
+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.
-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