Re: [ovs-dev] [RFC PATCH v1 1/3] OVN ACL: Replace the usage of ct_label with ct_mark

2019-02-06 Thread Ankur Sharma
- From: Ben Pfaff Sent: Tuesday, February 5, 2019 1:21 PM To: Ankur Sharma Cc: ovs-dev@openvswitch.org Subject: Re: [ovs-dev] [RFC PATCH v1 1/3] OVN ACL: Replace the usage of ct_label with ct_mark On Fri, Jan 11, 2019 at 12:16:35AM +, Ankur Sharma wrote: > OVN ACL implementation used ct_label

Re: [ovs-dev] [RFC PATCH v1 1/3] OVN ACL: Replace the usage of ct_label with ct_mark

2019-02-05 Thread Ben Pfaff
On Fri, Jan 11, 2019 at 12:16:35AM +, Ankur Sharma wrote: > OVN ACL implementation used ct_label to indicate if a previosuly > allowed connection shoudl not be allowed anymore and vice versa. > > However, ct_label is a 128 bit value and we should rather leverage > on ct_mark which is a 32 bit

[ovs-dev] [RFC PATCH v1 1/3] OVN ACL: Replace the usage of ct_label with ct_mark

2019-01-10 Thread Ankur Sharma
OVN ACL implementation used ct_label to indicate if a previosuly allowed connection shoudl not be allowed anymore and vice versa. However, ct_label is a 128 bit value and we should rather leverage on ct_mark which is a 32 bit value. Using ct_mark for this purpose, allows us to use ct_label for st