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 patch. > > Please explain why the artificial priorities are needed at all. > Hardware should order tables based on table type - ethtool, TC, nft. > As I mentioned in the first email, and unless you can make a strong > case against that. > Within those tables we should follow the same ordering rules as we > do in software (modulo ethtool but ordering is pretty clear there). 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. Drivers still need to be updated to support for more than one flow_block/subsystem binding at this stage though.
