jvpp-benchmark: add option to select interface mode

Changes:
- use loopback interface instead of local0,
- if L3 (default) mode is selected, assing IP to the loop0 interface,
- if L2 mode is selected, create bridge domain and assing loop0 the BD.

To test interface in L2 mode, use:

sudo java -jar ./target/jvpp-benchmark-exec.jar -p mode=L2

Change-Id: I8450d42fe0d164c6dbedf1dacf1444a25d9932b8
Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
(cherry picked from commit 6e5446c9d64df7f2cbde857d276e8685c9175089)

1 files changed, 7 insertions, 1 deletions

diff --git a/it/jvpp-benchmark/asciidoc/Readme.adoc b/it/jvpp-benchmark/asciidoc/Readme.adoc
index 604abf9b3..8c787d4ac 100644
--- a/it/jvpp-benchmark/asciidoc/Readme.adoc
+++ b/it/jvpp-benchmark/asciidoc/Readme.adoc
@@ -5,7 +5,7 @@ Provides JMH based benchmarks JVpp (Java API for VPP).
 == AclUpdateBenchmark
 
 Creates ACL of size aclSize using acl_add_replace,
-then assigns it to local0 using acl_interface_set_acl_list.
+then assigns it to loopback interface using acl_interface_set_acl_list.
 
 Then ACL is updated synchronously using acl_add_replace.
 By default 20x2s warmup and 100x2s measurment iterations
@@ -42,6 +42,12 @@ To specify aclSetSize (default=100), use:
 sudo java -jar ./target/jvpp-benchmark-exec.jar -p aclSetSize=1000
 ---
 
+To test interface in bridged (L2) / routed (L3) mode (default=L3), use:
+[source,shell]
+---
+sudo java -jar ./target/jvpp-benchmark-exec.jar -p mode=L2
+---
+
 To see more options, use
 [source,shell]
 ---