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

2019-09-06 Thread David Miller
From: Paul Blakey Date: Wed, 4 Sep 2019 16:56:37 +0300 > 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 f

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

2019-09-05 Thread Pravin Shelar
On Wed, Sep 4, 2019 at 6:56 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

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

2019-09-04 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