From 1d1103a25ce070b21bdfebcd90889e368e250615 Mon Sep 17 00:00:00 2001 From: Donald Sharp Date: Thu, 8 Dec 2022 16:31:50 -0500 Subject: [PATCH] doc: Clarify asic offload documentation in zebra Signed-off-by: Donald Sharp --- doc/user/zebra.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst index a78731ca94..230a4f43b0 100644 --- a/doc/user/zebra.rst +++ b/doc/user/zebra.rst @@ -68,7 +68,7 @@ Besides the common invocation options (:ref:`common-invocation-options`), the option and we will use Route Replace Semantics instead of delete than add. -.. option:: --asic-offload [notify_on_offload|notify_on_ack] +.. option:: --asic-offload=[notify_on_offload|notify_on_ack] The linux kernel has the ability to use asic-offload ( see switchdev development ). When the operator knows that FRR will be working in @@ -76,11 +76,12 @@ Besides the common invocation options (:ref:`common-invocation-options`), the code only supports asynchronous notification of the offload state. In other words the initial ACK received for linux kernel installation does not give zebra any data about what the state of the offload - is. This option takes the optional paramegers notify_on_offload + is. This option takes the optional parameters notify_on_offload or notify_on_ack. This signals to zebra to notify upper level protocols about route installation/update on ack received from the linux kernel or from offload notification. + .. option:: -s , --nl-bufsize Allow zebra to modify the default receive buffer size to SIZE -- 2.39.5