When this configuration parameter was initially introduced into the
database, the documentation was not updated to describe where it
resides.
Fixes: 72310b041cfa ("upcall: Configure datapath max-idle through ovs-vsctl.")
Reported-by: Hadar Hen Zion <had...@dev.mellanox.co.il>
Signed-off-by: Joe Stringer <joestrin...@nicira.com>
---
vswitchd/vswitch.xml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index c94f42d1399b..6a699e0da180 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -152,6 +152,19 @@
</p>
</column>
+ <column name="other_config" key="max-idle"
+ type='{"type": "integer", "minInteger": 500}'>
+ <p>
+ The maximum time (in ms) that idle flows will remain cached in the
+ datapath. Internally OVS will check the validity and activity for
+ datapath flows regularly and may expire flows quicker than this
+ number, based on real time network conditions.
+ </p>
+ <p>
+ The default is 10000.
+ </p>
+ </column>
+
<column name="other_config" key="n-dpdk-rxqs"
type='{"type": "integer", "minInteger": 1}'>
<p>
--
2.1.4
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
