On Thu, Apr 27, 2017 at 4:12 AM, Jiri Pirko <j...@resnulli.us> wrote: > Simple example: > $ tc qdisc add dev eth0 ingress > $ tc filter add dev eth0 parent ffff: protocol ip pref 33 flower dst_mac > 52:54:00:3d:c7:6d action goto chain 11 > $ tc filter add dev eth0 parent ffff: protocol ip pref 22 chain 11 flower > dst_ip 192.168.40.1 action drop > $ tc filter show dev eth0 root
Interesting. I don't look into the code yet. If I understand the concepts correctly, so with your patchset we can mark either filter with a chain No. to choose which chain it belongs to _logically_ even though _physically_ it is still in the old-fashion chain (prio, proto)? If so, you have to ensure proto is same since the protocol of the packet does not change dynamically? And the original priority becomes pointless with chains since we can just to any other chain in any order? By default, without any chain No., you use 0 for all the chains, so the old-fashion chain still works. Thanks.
