Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-20 Thread Paul Blakey
On 8/20/2019 8:50 AM, Pravin Shelar wrote: > On Mon, Aug 19, 2019 at 10:42 AM Marcelo Ricardo Leitner > wrote: >> On Sun, Aug 18, 2019 at 07:00:59PM +0300, Paul Blakey wrote: >>> What do you guys say about the following diff on top of the last one? >>> Use static key, and also have OVS_DP_CMD_SET

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-19 Thread Pravin Shelar
On Sun, Aug 18, 2019 at 9:01 AM Paul Blakey wrote: > > What do you guys say about the following diff on top of the last one? > Use static key, and also have OVS_DP_CMD_SET command probe/enable the feature. > > This will allow userspace to probe the feature, and selectivly enable it via > the > OV

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-19 Thread Pravin Shelar
On Mon, Aug 19, 2019 at 10:42 AM Marcelo Ricardo Leitner wrote: > > On Sun, Aug 18, 2019 at 07:00:59PM +0300, Paul Blakey wrote: > > What do you guys say about the following diff on top of the last one? > > Use static key, and also have OVS_DP_CMD_SET command probe/enable the > > feature. > > > >

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-19 Thread Marcelo Ricardo Leitner
On Sun, Aug 18, 2019 at 07:00:59PM +0300, Paul Blakey wrote: > What do you guys say about the following diff on top of the last one? > Use static key, and also have OVS_DP_CMD_SET command probe/enable the feature. > > This will allow userspace to probe the feature, and selectivly enable it via >

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-18 Thread Paul Blakey
On 8/18/2019 7:00 PM, Paul Blakey wrote: > What do you guys say about the following diff on top of the last one? > Use static key, and also have OVS_DP_CMD_SET command probe/enable the feature. > > This will allow userspace to probe the feature, and selectivly enable it via > the > OVS_DP_CMD_SET

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain

2019-08-18 Thread Paul Blakey
What do you guys say about the following diff on top of the last one? Use static key, and also have OVS_DP_CMD_SET command probe/enable the feature. This will allow userspace to probe the feature, and selectivly enable it via the OVS_DP_CMD_SET command. Thansk, Paul. --- include/uapi/linux/ope

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-14 Thread Pravin Shelar
On Tue, Aug 13, 2019 at 1:29 AM Paul Blakey wrote: > > > On 8/12/2019 7:18 PM, Pravin Shelar wrote: > > On Sun, Aug 11, 2019 at 3:46 AM Paul Blakey wrote: > >> > >> On 8/8/2019 11:53 PM, Pravin Shelar wrote: > >>> On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: > Offloaded OvS datapath ru

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-13 Thread Paul Blakey
On 8/12/2019 7:18 PM, Pravin Shelar wrote: > On Sun, Aug 11, 2019 at 3:46 AM Paul Blakey wrote: >> >> On 8/8/2019 11:53 PM, Pravin Shelar wrote: >>> On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: Offloaded OvS datapath rules are translated one to one to tc rules, for example the fol

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-12 Thread Pravin Shelar
On Sun, Aug 11, 2019 at 3:46 AM Paul Blakey wrote: > > > On 8/8/2019 11:53 PM, Pravin Shelar wrote: > > On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: > >> Offloaded OvS datapath rules are translated one to one to tc rules, > >> for example the following simplified OvS rule: > >> > >> recirc_i

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-11 Thread Paul Blakey
On 8/8/2019 11:53 PM, Pravin Shelar wrote: > On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: >> Offloaded OvS datapath rules are translated one to one to tc rules, >> for example the following simplified OvS rule: >> >> recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-trk) >> actions:ct()

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-11 Thread Paul Blakey
On 8/8/2019 11:53 PM, Pravin Shelar wrote: > On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: >> Offloaded OvS datapath rules are translated one to one to tc rules, >> for example the following simplified OvS rule: >> >> recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-trk) >> actions:ct()

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-08 Thread Pravin Shelar
On Wed, Aug 7, 2019 at 5:08 AM Paul Blakey wrote: > > Offloaded OvS datapath rules are translated one to one to tc rules, > for example the following simplified OvS rule: > > recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-trk) > actions:ct(),recirc(2) > > Will be translated to the followin

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-07 Thread Paul Blakey
On 8/7/2019 6:00 PM, Marcelo Ricardo Leitner wrote: > On Wed, Aug 07, 2019 at 03:08:42PM +0300, Paul Blakey wrote: >> Offloaded OvS datapath rules are translated one to one to tc rules, >> for example the following simplified OvS rule: >> >> recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-tr

Re: [PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-07 Thread Marcelo Ricardo Leitner
On Wed, Aug 07, 2019 at 03:08:42PM +0300, Paul Blakey wrote: > Offloaded OvS datapath rules are translated one to one to tc rules, > for example the following simplified OvS rule: > > recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-trk) > actions:ct(),recirc(2) > > Will be translated to th

[PATCH net-next] net: openvswitch: Set OvS recirc_id from tc chain index

2019-08-07 Thread Paul Blakey
Offloaded OvS datapath rules are translated one to one to tc rules, for example the following simplified OvS rule: recirc_id(0),in_port(dev1),eth_type(0x0800),ct_state(-trk) actions:ct(),recirc(2) Will be translated to the following tc rule: $ tc filter add dev dev1 ingress \ prio 1