diff options
author | Lior Nahmanson <liorna@nvidia.com> | 2022-09-06 08:21:21 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2022-09-07 16:02:08 +0300 |
commit | e467b283ffd50cf15b84c73eef68787e257eaed5 (patch) | |
tree | 7a343398b65fcb4ae9886f8a4f1bebc4e6efffa8 /fs | |
parent | ee534d7f81ba9cec028580f91429b3dc29b90c7f (diff) | |
download | linux-e467b283ffd50cf15b84c73eef68787e257eaed5.tar.xz |
net/mlx5e: Add MACsec TX steering rules
Tx flow steering consists of two flow tables (FTs).
The first FT (crypto table) has two fixed rules:
One default miss rule so non MACsec offloaded packets bypass the MACSec
tables, another rule to make sure that MACsec key exchange (MKE) traffic
passes unencrypted as expected (matched of ethertype).
On each new MACsec offload flow, a new MACsec rule is added.
This rule is matched on metadata_reg_a (which contains the id of the
flow) and invokes the MACsec offload action on match.
The second FT (check table) has two fixed rules:
One rule for verifying that the previous offload actions were
finished successfully and packet need to be transmitted.
Another default rule for dropping packets that were failed in the
offload actions.
The MACsec FTs should be created on demand when the first MACsec rule is
added and destroyed when the last MACsec rule is deleted.
Signed-off-by: Lior Nahmanson <liorna@nvidia.com>
Reviewed-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Raed Salem <raeds@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions