On Tue, 2019-02-05 at 14:59 -0800, David Ahern wrote:
> On 2/5/19 2:53 PM, Stephen Hemminger wrote:
> > On Thu, 31 Jan 2019 18:58:09 +0100
> > Davide Caratti wrote:
> >
> > > + print_uint(PRINT_ANY, "code", "%hu ", ops[i].code);
> > > + print_uint(PRINT_ANY, "jt", "%hhu ", ops[i].
On 2/5/19 2:53 PM, Stephen Hemminger wrote:
> On Thu, 31 Jan 2019 18:58:09 +0100
> Davide Caratti wrote:
>
>> +print_uint(PRINT_ANY, "code", "%hu ", ops[i].code);
>> +print_uint(PRINT_ANY, "jt", "%hhu ", ops[i].jt);
>> +print_uint(PRINT_ANY, "jf", "%hhu ", ops[
On Thu, 31 Jan 2019 18:58:09 +0100
Davide Caratti wrote:
> + print_uint(PRINT_ANY, "code", "%hu ", ops[i].code);
> + print_uint(PRINT_ANY, "jt", "%hhu ", ops[i].jt);
> + print_uint(PRINT_ANY, "jf", "%hhu ", ops[i].jf);
Did you know that print_uint promotes the
On 1/31/19 10:58 AM, Davide Caratti wrote:
> Add full JSON output support in the dump of 'act_bpf'.
>
> Example using eBPF:
>
> # tc actions flush action bpf
> # tc action add action bpf object bpf/action.o section 'action-ok'
> # tc -j action list action bpf | jq
> [
>{
> "total act
Add full JSON output support in the dump of 'act_bpf'.
Example using eBPF:
# tc actions flush action bpf
# tc action add action bpf object bpf/action.o section 'action-ok'
# tc -j action list action bpf | jq
[
{
"total acts": 1
},
{
"actions": [
{
"order": 0