Since the 'commit' flag is required to set the mark and/or labels, the set values are always available for following lookups.
Signed-off-by: Jarno Rajahalme <ja...@ovn.org> --- utilities/ovs-ofctl.8.in | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/utilities/ovs-ofctl.8.in b/utilities/ovs-ofctl.8.in index fad2709..6c91d04 100644 --- a/utilities/ovs-ofctl.8.in +++ b/utilities/ovs-ofctl.8.in @@ -1773,15 +1773,15 @@ modified with this option. For example: . .RS .IP \fBset_field:\fIvalue\fR[\fB/\fImask\fR]->ct_mark\fR -Store a 32-bit metadata value with the connection. If the connection is -committed, then subsequent lookups for packets in this connection will -populate the \fBct_mark\fR flow field when the packet is sent to the -connection tracker with the \fBtable\fR specified. +Store a 32-bit metadata value with the connection. Subsequent lookups +for packets in this connection will populate the \fBct_mark\fR flow +field when the packet is sent to the connection tracker with the +\fBtable\fR specified. .IP \fBset_field:\fIvalue\fR[\fB/\fImask\fR]->ct_label\fR -Store a 128-bit metadata value with the connection. If the connection is -committed, then subsequent lookups for packets in this connection will -populate the \fBct_label\fR flow field when the packet is sent to the -connection tracker with the \fBtable\fR specified. +Store a 128-bit metadata value with the connection. Subsequent +lookups for packets in this connection will populate the +\fBct_label\fR flow field when the packet is sent to the connection +tracker with the \fBtable\fR specified. .RE .IP The \fBcommit\fR parameter must be specified to use \fBexec(...)\fR. -- 2.1.4 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
