From 9a998f2dda2133d4ab66a088036c03c71e419a09 Mon Sep 17 00:00:00 2001 From: Reshma Pattan Date: Thu, 10 Nov 2016 16:29:50 +0000 Subject: [PATCH 1/1] doc: fix l3fwd mode selection The l3fwd application route lookup mode can be selected at run time but not at compile time. This patch corrects the statement in the doc. Fixes: d0dff9ba ("doc: sample application user guide") Signed-off-by: Reshma Pattan Acked-by: John McNamara --- doc/guides/sample_app_ug/l3_forward.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst index e2e622364e..ab916b971d 100644 --- a/doc/guides/sample_app_ug/l3_forward.rst +++ b/doc/guides/sample_app_ug/l3_forward.rst @@ -42,7 +42,7 @@ The initialization and run-time paths are very similar to those of the :doc:`l2_ The main difference from the L2 Forwarding sample application is that the forwarding decision is made based on information read from the input packet. -The lookup method is either hash-based or LPM-based and is selected at compile time. When the selected lookup method is hash-based, +The lookup method is either hash-based or LPM-based and is selected at run time. When the selected lookup method is hash-based, a hash object is used to emulate the flow classification stage. The hash object is used in correlation with a flow table to map each input packet to its flow at runtime. -- 2.20.1