Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-06 Thread Pablo Neira Ayuso
On Mon, Aug 05, 2019 at 12:04:39PM -0700, Jakub Kicinski wrote: > On Sat, 3 Aug 2019 09:08:54 +0200, Pablo Neira Ayuso wrote: > > The idea is that every subsystem (ethtool, tc, nf) sets up/binds its > > own flow_block object. And each flow_block object has its own priority > > range space. So whate

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-05 Thread Jakub Kicinski
On Sat, 3 Aug 2019 09:08:54 +0200, Pablo Neira Ayuso wrote: > The idea is that every subsystem (ethtool, tc, nf) sets up/binds its > own flow_block object. And each flow_block object has its own priority > range space. So whatever priority the user specifies only applies to > the specific subsystem

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-03 Thread Pablo Neira Ayuso
Hi Jakub, On Fri, Aug 02, 2019 at 03:25:49PM -0700, Jakub Kicinski wrote: > On Sat, 3 Aug 2019 00:04:09 +0200, Pablo Neira Ayuso wrote: > > That patch removed the reference to tcf_auto_prio() already, please > > let me know if you have any more specific update you would like to see > > on that pat

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-02 Thread Jakub Kicinski
On Sat, 3 Aug 2019 00:04:09 +0200, Pablo Neira Ayuso wrote: > That patch removed the reference to tcf_auto_prio() already, please > let me know if you have any more specific update you would like to see > on that patch. Please explain why the artificial priorities are needed at all. Hardware shoul

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-02 Thread Pablo Neira Ayuso
Hi Jakub, On Fri, Aug 02, 2019 at 01:47:38PM -0700, Jakub Kicinski wrote: > On Fri, 2 Aug 2019 13:00:23 +0200, Pablo Neira Ayuso wrote: > > Hi Jakub, > > > > If the user specifies 'pref' in the new rule, then tc checks if there > > is a tcf_proto object that matches this priority. If the tcf_prot

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-02 Thread Jakub Kicinski
On Fri, 2 Aug 2019 13:00:23 +0200, Pablo Neira Ayuso wrote: > Hi Jakub, > > If the user specifies 'pref' in the new rule, then tc checks if there > is a tcf_proto object that matches this priority. If the tcf_proto > object does not exist, tc creates a tcf_proto object and it adds the > new rule t

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-02 Thread Pablo Neira Ayuso
Hi Jakub, If the user specifies 'pref' in the new rule, then tc checks if there is a tcf_proto object that matches this priority. If the tcf_proto object does not exist, tc creates a tcf_proto object and it adds the new rule to this tcf_proto. In cls_flower, each tcf_proto only stores one single

Re: [PATCH net 0/2] flow_offload hardware priority fixes

2019-08-01 Thread Jakub Kicinski
On Thu, 1 Aug 2019 13:28:15 +0200, Pablo Neira Ayuso wrote: > Please, apply, thank you. I'm still waiting for a reply. Perhaps since Pablo doesn't want to talk to me someone else can explain to me why we want to seemingly diverge from the software model?

[PATCH net 0/2] flow_offload hardware priority fixes

2019-08-01 Thread Pablo Neira Ayuso
Hi, This patchset contains two updates for the flow_offload users: 1) Pass the major tc priority to drivers so they do not have to lshift it. This is a preparation patch for the fix coming in patch #2. 2) Set the hardware priority from the netfilter basechain priority, some drivers brea