Document the "ovs-appctl dpif-netdev/miniflow-parser-get" and
"ovs-appctl dpif-netdev/miniflow-parser-set" commands in the vswitchd
manpage.
Fixes: 3d8f47bc041a ("dpif-netdev: Add command line and function pointer for
miniflow extract")
Signed-off-by: Cian Ferriter <[email protected]>
---
v2:
- Add one line summary in commit message.
- Reword miniflow-parser-set text to make default behavior more clear.
---
lib/dpif-netdev-unixctl.man | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/lib/dpif-netdev-unixctl.man b/lib/dpif-netdev-unixctl.man
index e8d904437..607750bad 100644
--- a/lib/dpif-netdev-unixctl.man
+++ b/lib/dpif-netdev-unixctl.man
@@ -249,3 +249,14 @@ Lists the DPIF implementations that are available.
.
.IP "\fBdpif-netdev/dpif-impl-set\fR \fIdpif_impl\fR"
Sets the DPIF to be used to \fIdpif_impl\fR. By default "dpif_scalar" is used.
+.
+.IP "\fBdpif-netdev/miniflow-parser-get\fR
+Lists the miniflow extract implementations that are available.
+.
+.IP "\fBdpif-netdev/miniflow-parser-set\fR [\fB-pmd\fR \fIcore\fR] \
+\fIminiflow_impl\fR [\fIstudy_cnt\fR]"
+Sets the miniflow extract to \fIminiflow_impl\fR for a specified PMD or all
+PMDs in the case where no value is specified. By default "scalar" is used.
+\fIstudy_cnt\fR defaults to 128 and indicates the number of packets that the
+"study" miniflow implementation must parse before choosing an optimal
+implementation.
--
2.32.0
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
