X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=7739793cfb13709a1272296c5a39d4dd6669e115;hb=1158389afa233c7191ba8f53820d7b128d9347fe;hp=fb9aa6d6dd568404e77fa4829af683045c35f895;hpb=e764773ccb007e79f44d948a781fae1313ac28fe;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index fb9aa6d6..7739793c 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -87,14 +87,6 @@
configuration changes.
-
The statistics
column contains key-value pairs that
@@ -467,7 +459,7 @@
on bridges. Bond, internal, and mirror ports are not supported
and will not participate in the spanning tree.
-
+
ipsec_gre
capwap
ovs-appctl
command.
+ + VLAN splinters do not support 802.1p priority tags. Received + priorities will appear to be 0, regardless of their actual values, + and priorities on transmitted packets will also be cleared to 0. +
The type of QoS to implement. The column in the table - identifies the types that a switch actually supports. The currently - defined types are listed below:
+The type of QoS to implement. The currently defined types are + listed below:
linux-htb
queue_id
used in
OpenFlow in struct ofp_action_enqueue
and other
- structures. Queue 0 is used by OpenFlow output actions that do not
- specify a specific queue.
+ structures.
+
+ + Queue 0 is the ``default queue.'' It is used by OpenFlow output + actions when no specific queue has been set. When no configuration for + queue 0 is present, it is automatically configured as if a record with empty + and columns had been + specified. + (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in + this case. With some queuing disciplines, this dropped all packets + destined for the default queue.) +
linux-htb
and linux-hfsc
classes support
the following key-value pair:
-
+
linux-htb
may use queue_id
s less than 61440.
It has the following key-value pairs defined.
-
+
linux-hfsc
may use queue_id
s less than 61440.
It has the following key-value pairs defined.
-
+
+ OpenFlow switches send certain messages to controllers spontanenously, + that is, not in response to any request from the controller. These + messages are called ``asynchronous messages.'' These columns allow + asynchronous messages to be limited or disabled to ensure the best use + of network resources. +
+ +false
to change Open vSwitch behavior to disable, by
+ default, all asynchronous messages. The controller can use the
+ NXT_SET_ASYNC_CONFIG
Nicira extension to OpenFlow to turn
+ on any messages that it does want to receive, if any.
+ The maximum rate at which packets in unknown flows will be - forwarded to the OpenFlow controller, in packets per second. This - feature prevents a single bridge from overwhelming the controller. - If not specified, the default is implementation-specific.
-In addition, when a high rate triggers rate-limiting, Open - vSwitch queues controller packets for each port and transmits - them to the controller at the configured rate. The number of - queued packets is limited by - the value. The packet - queue is shared fairly among the ports on a bridge.
Open - vSwitch maintains two such packet rate-limiters per bridge. - One of these applies to packets sent up to the controller - because they do not correspond to any flow. The other applies - to packets sent up to the controller by request through flow - actions. When both rate-limiters are filled with packets, the - actual rate that packets are sent to the controller is up to - twice the specified rate.
++ The maximum rate at which the switch will forward packets to the + OpenFlow controller, in packets per second. This feature prevents a + single bridge from overwhelming the controller. If not specified, + the default is implementation-specific. +
+ ++ In addition, when a high rate triggers rate-limiting, Open vSwitch + queues controller packets for each port and transmits them to the + controller at the configured rate. The value limits the number of queued + packets. Ports on a bridge share the packet queue fairly. +
+ ++ Open vSwitch maintains two such packet rate-limiters per bridge: one + for packets sent up to the controller because they do not correspond + to any flow, and the other for packets sent up to the controller by + request through flow actions. When both rate-limiters are filled with + packets, the actual rate that packets are sent to the controller is + up to twice the specified rate. +