[ovs-dev] [PATCH] docs: fix the documentation of n-handler-threads and n-revalidator-threads
Matteo Croce
mcroce at redhat.com
Tue Feb 6 14:44:52 UTC 2018
Documentation for both n-handler-threads and n-revalidator-threads was
wrong, the spawned threads are per port instead of per datapath.
Update the docs according to vswitchd/ovs-vswitchd.8.in and code behaviour.
Signed-off-by: Matteo Croce <mcroce at redhat.com>
---
vswitchd/vswitch.xml | 16 +++++-----------
1 file changed, 5 insertions(+), 11 deletions(-)
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 0c6a43d60..4b3d7610a 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -379,15 +379,12 @@
type='{"type": "integer", "minInteger": 1}'>
<p>
Specifies the number of threads for software datapaths to use for
- handling new flows. The default the number of online CPU cores minus
+ handling new flows. The default is the number of online CPU cores minus
the number of revalidators.
</p>
<p>
- This configuration is per datapath. If you have more than one
- software datapath (e.g. some <code>system</code> bridges and some
- <code>netdev</code> bridges), then the total number of threads is
- <code>n-handler-threads</code> times the number of software
- datapaths.
+ This configuration is per port, the total number of threads is
+ <code>n-handler-threads</code> times the number of ports.
</p>
</column>
@@ -403,11 +400,8 @@
of handler threads.
</p>
<p>
- This configuration is per datapath. If you have more than one
- software datapath (e.g. some <code>system</code> bridges and some
- <code>netdev</code> bridges), then the total number of threads is
- <code>n-handler-threads</code> times the number of software
- datapaths.
+ This configuration is per port: the total number of threads is
+ <code>n-revalidator-threads</code> times the number of ports.
</p>
</column>
--
2.14.3
More information about the dev
mailing list