Re: [PATCHv3 net-next 06/10] openvswitch: Allow matching on conntrack mark

2015-08-13 Thread Pravin Shelar
On Wed, Aug 12, 2015 at 4:41 PM, Joe Stringer joestrin...@nicira.com wrote: On 12 August 2015 at 16:00, Pravin Shelar pshe...@nicira.com wrote: On Tue, Aug 11, 2015 at 3:59 PM, Joe Stringer joestrin...@nicira.com wrote: From: Justin Pettit jpet...@nicira.com Allow matching and setting the

Re: [PATCHv3 net-next 06/10] openvswitch: Allow matching on conntrack mark

2015-08-12 Thread Joe Stringer
On 12 August 2015 at 16:00, Pravin Shelar pshe...@nicira.com wrote: On Tue, Aug 11, 2015 at 3:59 PM, Joe Stringer joestrin...@nicira.com wrote: From: Justin Pettit jpet...@nicira.com Allow matching and setting the conntrack mark field. As with conntrack state and zone, these are populated by

Re: [PATCHv3 net-next 06/10] openvswitch: Allow matching on conntrack mark

2015-08-12 Thread Pravin Shelar
On Tue, Aug 11, 2015 at 3:59 PM, Joe Stringer joestrin...@nicira.com wrote: From: Justin Pettit jpet...@nicira.com Allow matching and setting the conntrack mark field. As with conntrack state and zone, these are populated by executing the ct() action. Unlike these, the ct_mark is also a

[PATCHv3 net-next 06/10] openvswitch: Allow matching on conntrack mark

2015-08-11 Thread Joe Stringer
From: Justin Pettit jpet...@nicira.com Allow matching and setting the conntrack mark field. As with conntrack state and zone, these are populated by executing the ct() action. Unlike these, the ct_mark is also a writable field. The set_field() action may be used to modify the mark, which will