On 2 September 2014 22:48, Joe Stringer <joestrin...@nicira.com> wrote:
> If a datapath is created with the flag OVS_DP_F_INDEX_BY_UID, then an
> additional table_instance is added to the flow_table, which is indexed
> by unique identifiers ("UID"). This can be manipulated using the flow
> key as before, or by using the new UID field. If both are specified,
> then UID takes precedence. UIDs up to 128 bits may be specified for any
> flow operation.
>
> If a datapath is created using OVS_DP_F_INDEX_BY_UID and a UID is not
> specified at flow setup time, then that operation will fail. If
> OVS_UID_F_* flags are specified for an operation, then they will modify
> what is returned through the operation. For instance, OVS_UID_F_SKIP_KEY
> allows the datapath to skip returning the key.
>
> Signed-off-by: Joe Stringer <joestrin...@nicira.com>
> ---
>
> If the datapath is created using OVS_DP_F_INDEX_BY_UID then a user
> starts an older userspace (with no support for UID), the older userspace
> will be unable to install flows until the kernel module is reloaded.
>
> v3: Initial post.
>
I'm fixing the memory leaks in this patch, but I'd welcome any feedback on
the rest of it in the mean time.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
