From 4530afbaf4e5fbf8f9b3e2832fb9c89f618225e5 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 30 Apr 2012 11:32:13 -0700 Subject: [PATCH] ovs-ofctl: Document importance of priorities. Multiple users have asked me about this. Signed-off-by: Ben Pfaff --- utilities/ovs-ofctl.8.in | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/utilities/ovs-ofctl.8.in b/utilities/ovs-ofctl.8.in index 18769290..4164bc9e 100644 --- a/utilities/ovs-ofctl.8.in +++ b/utilities/ovs-ofctl.8.in @@ -1098,6 +1098,13 @@ others. \fIvalue\fR is a number between 0 and 65535, inclusive. A higher have priority over an entry containing wildcards, so it has an implicit priority value of 65535. When adding a flow, if the field is not specified, the flow's priority will default to 32768. +.IP +OpenFlow leaves behavior undefined when two or more flows with the +same priority can match a single packet. Some users expect +``sensible'' behavior, such as more specific flows taking precedence +over less specific flows, but OpenFlow does not specify this and Open +vSwitch does not implement it. Users should therefore take care to +use priorities to ensure the behavior that they expect. . .PP The \fBadd\-flow\fR, \fBadd\-flows\fR, and \fBmod\-flows\fR commands -- 2.30.2