[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBGUJt+fJ61yRKUB@Laptop-X1>
Date: Wed, 15 Mar 2023 17:47:18 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: netdev@...r.kernel.org, Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
David Ahern <dsahern@...nel.org>,
Stephen Hemminger <stephen@...workplumber.org>,
Davide Caratti <dcaratti@...hat.com>,
Pedro Tammela <pctammela@...atatu.com>,
Marcelo Leitner <mleitner@...hat.com>,
Phil Sutter <psutter@...hat.com>
Subject: Re: [PATCH net 2/2] net/sched: act_api: add specific EXT_WARN_MSG
for tc action
On Tue, Mar 14, 2023 at 06:35:29PM -0400, Jamal Hadi Salim wrote:
> Sorry, only thing i should have mentioned earlier - not clear from here:
> Do you get two ext warns now in the same netlink message? One for the
> action and one for the cls?
> Something to check:
> on terminal1 > tc monitor
> on terminal2 > run a command which will get the offload to fail and
> see what response you get
>
> My concern is you may be getting two warnings in one message.
>From the result we only got 1 warning message.
# tc qdisc add dev enp4s0f0np0 ingress
# tc filter add dev enp4s0f0np0 ingress flower verbose ct_state +trk+new action drop
Warning: mlx5_core: matching on ct_state +new isn't supported.
# tc monitor
qdisc ingress ffff: dev enp4s0f0np0 parent ffff:fff1 ----------------
added chain dev enp4s0f0np0 parent ffff: chain 0
added filter dev enp4s0f0np0 ingress protocol all pref 49152 flower chain 0 handle 0x1
ct_state +trk+new
not_in_hw
action order 1: gact action drop
random type none pass val 0
index 1 ref 1 bind 1
mlx5_core: matching on ct_state +new isn't supported
^C
Thanks
Hangbin
Powered by blists - more mailing lists