On 12/07/2015 03:19 AM, Luuk Paulussen wrote:
On 12/07/2015 11:45 AM, Florian Westphal wrote:
Luuk Paulussen <Luuk.Paulussen@xxxxxxxxxxxxxxxxxxx> wrote:
Hi All,
I'm still hoping for some feedback on this. I have some userspace
patches around this as well, (to set/show the tc_index in the
connection, and to add the marking/matching rules in iptables), but I am
holding off on sending them until I know what people think of this
idea/implementation first.
I can't say for sure since I don't know enough about tc.
However, AFAICS tc_index seems to be something that should be internal
to tc and not exposed/changeable via iptables.
tc_index is a mark that can be set by certain configurable ingress
schedulers (dsmark, GRED, ingress) for later classification via the
tcindex classifer. This just adds an alternative mechanism for setting
this mark if those schedulers aren't being used.
Fwiw, tc_index can be read/written by cls_bpf (and you can also apply masks
on that field if needed).
* dsmark sets the tc_index value based on the incoming DSCP value
* ingress sets the tc_index value based on other rules (e.g. mark set
via iptables)
* New code sets tc_index directly based on iptables classification or
restoring saved value.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
