[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200330.110705.1840847675396461402.davem@davemloft.net>
Date: Mon, 30 Mar 2020 11:07:05 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, kuba@...nel.org, idosch@...lanox.com,
saeedm@...lanox.com, leon@...nel.org, michael.chan@...adcom.com,
vishal@...lsio.com, pablo@...filter.org, jhs@...atatu.com,
xiyou.wangcong@...il.com, paulb@...lanox.com,
alexandre.belloni@...tlin.com, ozsh@...lanox.com,
roid@...lanox.com, john.hurley@...ronome.com,
simon.horman@...ronome.com, pieter.jansenvanvuuren@...ronome.com
Subject: Re: [patch net-next 0/2] net: sched: expose HW stats types per
action used by drivers
From: Jiri Pirko <jiri@...nulli.us>
Date: Sat, 28 Mar 2020 16:37:41 +0100
> From: Jiri Pirko <jiri@...lanox.com>
>
> The first patch is just adding a helper used by the second patch too.
> The second patch is exposing HW stats types that are used by drivers.
>
> Example:
>
> $ tc filter add dev enp3s0np1 ingress proto ip handle 1 pref 1 flower dst_ip 192.168.1.1 action drop
> $ tc -s filter show dev enp3s0np1 ingress
> filter protocol ip pref 1 flower chain 0
> filter protocol ip pref 1 flower chain 0 handle 0x1
> eth_type ipv4
> dst_ip 192.168.1.1
> in_hw in_hw_count 2
> action order 1: gact action drop
> random type none pass val 0
> index 1 ref 1 bind 1 installed 10 sec used 10 sec
> Action statistics:
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> backlog 0b 0p requeues 0
> used_hw_stats immediate <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Series applied, thanks Jiri.
Powered by blists - more mailing lists