[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMDZJNXcya=6VsXitukS5MmZ36oPCUVNMncBJKrWmzwK62LeUg@mail.gmail.com>
Date: Thu, 5 Dec 2019 14:41:06 +0800
From: Tonghao Zhang <xiangxia.m.yue@...il.com>
To: Roi Dayan <roid@...lanox.com>, Saeed Mahameed <saeedm@...lanox.com>
Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: mlx5 support tc accept action
Hi Roi, Saeed
In one cause, we want the "accept" action: the IP of VF will be
"accept", and others
packets will be done with other actions(e.g. hairpin rule to other VF).
For example:
PF0=enp130s0f0
VF0_REP=enp130s0f0_0
VF0=p4p1_0
VF1=p4p2_0 # belong to PF1
VF0_IP=3.3.3.200
ethtool -K $PF0 hw-tc-offload on
ethtool -K $VF0 hw-tc-offload on
tc qdisc add dev $PF0 ingress
tc qdisc add dev $VF0 ingress
tc filter add dev $PF0 protocol all parent ffff: prio 10 handle 1
flower skip_sw action mirred egress redirect dev $VF0_REP
tc filter add dev $VF0 protocol ip parent ffff: prio 1 handle 3 flower
skip_sw dst_ip $VF0_IP action pass
tc filter add dev $VF0 protocol all parent ffff: prio 10 handle 2
flower skip_sw action mirred egress redirect dev $VF1
When I change the driver, the rule which action "action pass", can be
offloaded, but it didn't work.
+ case FLOW_ACTION_ACCEPT:
+ action |= MLX5_FLOW_CONTEXT_ACTION_ALLOW;
+ break;
How can we support it, this function is import for us.
Powered by blists - more mailing lists