[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdb0ae4d-b488-b305-4146-e938e8b560f4@ucloud.cn>
Date: Mon, 16 Mar 2020 16:23:03 +0800
From: wenxu <wenxu@...oud.cn>
To: Paul Blakey <paulb@...lanox.com>
Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: ct_act can't offload in hardware
Hi paul,
I test the ct offload with tc in net-next branch and meet some problem
gre_sys is a getap device.
# tc filter add dev gre_sys ingress prio 2 chain 0 proto ip flower enc_dst_ip 172.168.152.75 enc_src_ip 172.168.152.208 enc_key_id 1000 enc_tos 0x0/ff dst_ip 1.1.1.7 ct_state -trk action ct zone 1 nat pipe action goto chain 1
The rule show is not_in_hw
# tc filter ls dev gre_sys ingress
filter protocol ip pref 2 flower chain 0
filter protocol ip pref 2 flower chain 0 handle 0x1
eth_type ipv4
dst_ip 1.1.1.7
enc_dst_ip 172.168.152.75
enc_src_ip 172.168.152.208
enc_key_id 1000
enc_tos 0x0/ff
ct_state -trk
not_in_hw
action order 1: ct zone 1 nat pipe
index 1 ref 1 bind 1
action order 2: gact action goto chain 1
random type none pass val 0
index 1 ref 1 bind 1
# dmesg
mlx5_core 0000:81:00.0 net2: Chains on tunnel devices isn't supported without register metadata support
I update the fw to 16.27.1016 and also the problem is exist.
# ethtool -i net2
driver: mlx5e_rep
version: 5.6.0-rc5+
firmware-version: 16.27.1016 (MT_0000000080)
expansion-rom-version:
bus-info: 0000:81:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
Are there aome method to enable the register metadata support?
BR
wenxu
Powered by blists - more mailing lists