On 18-01-11 11:15 AM, Jiri Pirko wrote:
Thu, Jan 11, 2018 at 04:44:32PM CET, j...@mojatatu.com wrote:
On 18-01-11 10:07 AM, Jiri Pirko wrote:
Thu, Jan 11, 2018 at 03:46:09PM CET, j...@mojatatu.com wrote:
On 18-01-11 09:41 AM, Jiri Pirko wrote:
Thu, Jan 11, 2018 at 03:37:08PM CET, j...@mojatatu.com wrote:
I only looked at the kernel code. Good you can stop it at tc
but the API does not stop it (unless you expect the rest of the
world to only use tc).
Jamal, apparently, you did not looked at the kernel code either :)
Look at the changes done in net/sched/sch_ingress.c - there is where the
parsing of block attr takes place.
reason i raised it is from looking at tc_ctl_tfilter().
If i specify ifindex != TCM_IFINDEX_MAGIC_BLOCK,
parent = 0XFFFF.... and block = 22 that should work, no?
i.e regardless of whether parent is INGRESS etc.
No, the block needs to be created first by qdisc instance.
Seems to me that you are mixing apples and oranges a bit.
You are correct, the qdisc attachment must exist first ;->
TCA_BLOCK sounds appealing - could be a speacial tlv with many block ids
maybe? I really would like to use this for egress as well - and what
i described earlier should work for me.
I don't get what you mean by "tlv with many block ids". What is it good
for? :O
I meant A TLV with a bunch of 32 bit values, so you can have more than
one block id in it. But what Roopa suggested is more explicit (and
better).
cheers,
jamal
