When an interface has QoS configured but no default queue (queue 0), OVS
has until now installed that QoS configuration literally, which causes all
packets destined for this default queue to be dropped. This behavior is
usually both unexpected and undesirable.
This commit changes behavior so that, when no default queue is configured,
OVS uses a default "empty" configuration for the default queue. This
behavior should be more acceptable when QoS is slightly misconfigured.
I tested that, without this patch, configuring only queue 1 causes "tc
class show" to show only queue 1 (handle 1:2) for linux-htb and linux-hfsc,
and that with this patch it shows configurations for both queue 0 (handle
1:1) and queue 1.
Bug #5583.
Feature #7413.
Signed-off-by: Ben Pfaff <b...@nicira.com>
---
NEWS | 3 +++
vswitchd/bridge.c | 7 +++++--
vswitchd/vswitch.xml | 12 ++++++++++--
3 files changed, 18 insertions(+), 4 deletions(-)
diff --git a/NEWS b/NEWS
index a9cb1af..c2eb65d 100644
--- a/NEWS
+++ b/NEWS
@@ -18,6 +18,9 @@ post-v1.5.0
receive asynchronously.
- The default MAC learning timeout has been increased from 60 seconds
to 300 seconds. The MAC learning timeout is now configurable.
+ - When QoS settings for an interface do not configure a default queue
+ (queue 0), Open vSwitch now uses a default configuration for that
+ queue, instead of dropping all packets as in previous versions.
- Logging to console and file will have UTC timestamp as a default for all
the daemons. An example of the default format is 2012-01-27T16:35:17Z.
ovs-appctl can be used to change the default format as before.
diff --git a/vswitchd/bridge.c b/vswitchd/bridge.c
index f6cf119..e857077 100644
--- a/vswitchd/bridge.c
+++ b/vswitchd/bridge.c
@@ -3198,9 +3198,12 @@ iface_configure_qos(struct iface *iface, const struct
ovsrec_qos *qos)
if (!queue_zero) {
static struct vlog_rate_limit rl = VLOG_RATE_LIMIT_INIT(1, 1);
VLOG_WARN_RL(&rl, "interface %s: QoS configured without a default "
- "queue (queue 0). Packets not directed to a "
- "correctly configured queue may be dropped.",
+ "queue (queue 0). Using default configuration.",
iface->name);
+
+ shash_init(&details);
+ netdev_set_queue(iface->netdev, 0, &details);
+ shash_destroy(&details);
}
}
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index a248d9f..ce477e2 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -2067,8 +2067,16 @@
supported range of queue numbers depend on <ref column="type"/>. The
queue numbers are the same as the <code>queue_id</code> used in
OpenFlow in <code>struct ofp_action_enqueue</code> and other
- structures. Queue 0 is used by OpenFlow output actions that do not
- specify a specific queue.</p>
+ structures.</p>
+
+ <p>
+ Queue 0 is the ``default queue.'' It is used by OpenFlow output
+ actions when no specific queue has been set. Ordinarily <ref
+ column="queues"/> should include a configuration for queue 0. When no
+ configuration for queue 0 is present, a default configuration is used.
+ (Before version 1.6, Open vSwitch would drop all packets destined for
+ the default queue if no configuration was present.)
+ </p>
</column>
<group title="Configuration for linux-htb and linux-hfsc">
--
1.7.2.5
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
