@@ -283,6 +283,44 @@
</p>
</column>
+ <column name="other_config" key="keepalive"
+ type='{"type": "boolean"}'>
+ <p>
+ Set this value to <code>true</code> to enable keepalive feature.
+ </p>
+ <p>
+ The default value is <code>false</code>. Changing this value requires
+ restarting the daemon.
+ </p>
+ <p>
+ If this value is <code>false</code> at startup, keepalive thread
+ shall not be spawned.
+ </p>
+ </column>
+
+ <column name="other_config" key="keepalive-interval"
+ type='{"type": "integer", "minInteger": 1}'>
+ <p>
+ Specifies the keepalive interval value.
+ </p>
+ <p>
+ If not specified, this will be set to 100 milliseconds (default
+ value). Changing this value requires restarting the daemon.
+ </p>
+ </column>
+
+ <column name="other_config" key="keepalive-shm-name"
+ type='{"type": "string"}'>
+ <p>
+ Specifies the keepalive shared memory block name.
+ </p>
+ <p>
+ If not specified, shared memory block named "keepalive_shm_name"
+ (default name) is created. Changing this value requires restarting
+ the daemon.
+ </p>
+ </column>
+
<column name="other_config" key="dpdk-extra"
type='{"type": "string"}'>
<p>
Add support for keepalive functionality to DPDK datapath. By default, the keepalive is OFF and can be enabled/disabled either at start time. For eg: To enable keepalive feature. 'ovs-vsctl --no-wait set Open_vSwitch . other_config:keepalive=true' To set timer interval of 50ms for monitoring packet processing cores; 'ovs-vsctl --no-wait set Open_vSwitch . \ other_config:keepalive-interval="50" To set shared memory block name where the events shall be updated 'ovs-vsctl --no-wait set Open_vSwitch . other_config:keepalive-shm-name="/dpdk_keepalive_shm_name"' Signed-off-by: Bhanuprakash Bodireddy <bhanuprakash.bodireddy@intel.com> --- vswitchd/vswitch.xml | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+)