On Mon, Jun 13, 2016 at 02:00:19PM +0530, bscha...@redhat.com wrote:
> Linux ``No operation'' qos type is used to inform the vswitch that the
> traffic control for the port is managed externally. Any configuration values
> set for this type will have no effect.
>
> This patch provides a solution suggested in this mail -
> http://openvswitch.org/pipermail/discuss/2015-May/017687.html
>
> Signed-off-by: Babu Shanmugam <bscha...@redhat.com>
Thanks, this is useful.
I folded in the following incremental and applied this to master.
--8<--------------------------cut here-------------------------->8--
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 25c8e61..7ae0b51 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -3384,13 +3384,11 @@
<dt><code>linux-noop</code></dt>
<dd>
- <p>
- Linux ``No operation.'' By default, Open vSwitch manages quality
- of service on all of its configured ports. This can be helpful,
- but sometimes administrators prefer to use other software to manage
- QoS. This <ref column="type"/> prevents Open vSwitch from changing
- the QoS configuration for a port.
- </p>
+ Linux ``No operation.'' By default, Open vSwitch manages quality of
+ service on all of its configured ports. This can be helpful, but
+ sometimes administrators prefer to use other software to manage QoS.
+ This <ref column="type"/> prevents Open vSwitch from changing the QoS
+ configuration for a port.
</dd>
<dt><code>egress-policer</code></dt>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
