[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YOLh4U4JM7lcursX@fedora>
Date: Mon, 5 Jul 2021 18:41:37 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Roi Dayan <roid@...dia.com>
Cc: netdev@...r.kernel.org, Paul Blakey <paulb@...dia.com>,
David Ahern <dsahern@...il.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Roman Mashak <mrv@...atatu.com>,
Davide Caratti <dcaratti@...hat.com>,
Baowen Zheng <baowen.zheng@...igine.com>
Subject: Re: [PATCH iproute2-next v4 1/1] police: Add support for json output
On Mon, Jun 07, 2021 at 09:44:08AM +0300, Roi Dayan wrote:
> Change to use the print wrappers instead of fprintf().
>
> This is example output of the options part before this commit:
>
> "options": {
> "handle": 1,
> "in_hw": true,
> "actions": [ {
> "order": 1 police 0x2 ,
> "control_action": {
> "type": "drop"
> },
> "control_action": {
> "type": "continue"
> }overhead 0b linklayer unspec
> ref 1 bind 1
> ,
> "used_hw_stats": [ "delayed" ]
> } ]
> }
>
> This is the output of the same dump with this commit:
>
> "options": {
> "handle": 1,
> "in_hw": true,
> "actions": [ {
> "order": 1,
> "kind": "police",
> "index": 2,
> "control_action": {
> "type": "drop"
> },
> "control_action": {
> "type": "continue"
> },
> "overhead": 0,
> "linklayer": "unspec",
> "ref": 1,
> "bind": 1,
> "used_hw_stats": [ "delayed" ]
> } ]
> }
>
> Signed-off-by: Roi Dayan <roid@...dia.com>
> Reviewed-by: Paul Blakey <paulb@...dia.com>
> ---
[...]
>
> @@ -300,13 +301,13 @@ static int print_police(struct action_util *a, FILE *f, struct rtattr *arg)
> RTA_PAYLOAD(tb[TCA_POLICE_RATE64]) >= sizeof(rate64))
> rate64 = rta_getattr_u64(tb[TCA_POLICE_RATE64]);
>
> - fprintf(f, " police 0x%x ", p->index);
> + print_uint(PRINT_ANY, "index", "\t index %u ", p->index);
Hi everyone,
This update break all policy checking in kernel tc selftest actions/police.json.
As the new output would like
total acts 1
action order 0: police index 1 rate 1Kbit burst 10Kb mtu 2Kb action reclassify overhead 0 ref 1 bind 0
And the current test checks like
"matchPattern": "action order [0-9]*: police 0x1 rate 1Kbit burst 10Kb"
I plan to update the kselftest to mach the new output. But I have a question.
Why need we add a "\t" before index output? Is it needed or could be removed?
Thanks
Hangbin
Powered by blists - more mailing lists