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.
Right, okay so that part is pretty obvious but thanks for spelling it out. Are you also agreeing that priorities of blocks, not rules within a block are dictated by the order of processing within the kernel? IOW TC blocks are _always_ before nft blocks? > Drivers still need to be updated to support for more than one > flow_block/subsystem binding at this stage though.
