On 2020-06-23 7:55 a.m., Po Liu wrote:
[..]
My question: Is this any different from how stats are structured?
I don't know I fully catch the question. Are you trying to get how many frames
for each filter chain passing one index policing action?
If one index police action bind to multiple tc filter(they should have differnt
chain index ). All those filter should get same index police action stats value
since they are sharing the same hardware entry. But I don't think this is the
problem.
This is a good thing. What is nice is i can use the same index for
s/w and h/w (and no need for a translation/remapping).
With index provide to device driver(map the s/w action index to a h/w table
index ), user could list the police actions list by command:
# tc actions show action police
Shows the police action table by index.
This is also nice.
My question: Why cant you apply the same semantics for the counters?
Does your hardware have an indexed counter/stats table? If yes
then you should be able to do similar thing for counters
as you do for policer (i.e use an index and share counters across
actions). So when i say:
tc action drop index 5
and
tc action ok index 5
infact they use the same counter.
cheers,
jamal
