The title is confusing.
Port representor is already supported in mlx5.
It seems you are adding support for matching on port representor ID, right?
19/10/2022 16:57, Sean Zhang:
> Add support for port_representor item, it will match on traffic
> originated from representor port specified in the pa
enko
> ; dev@dpdk.org
> Subject: Re: [PATCH] net/mlx5: add port representor support
>
> External email: Use caution opening links or attachments
>
>
> Hi,
>
> This patch might be missing the following part:
>
> diff --git a/doc/guides/nics/features/mlx5.ini
&g
Hi,
This patch might be missing the following part:
diff --git a/doc/guides/nics/features/mlx5.ini
b/doc/guides/nics/features/mlx5.ini
index e5974063c8..5644626f06 100644
--- a/doc/guides/nics/features/mlx5.ini
+++ b/doc/guides/nics/features/mlx5.ini
@@ -84,6 +84,7 @@ vlan = Y
Add support for port_representor item, it will match on traffic
originated from representor port specified in the pattern. This item
is supported in FDB steering domain only (in the flow with transfer
attribute).
For example, below flow will redirect the destination of traffic from
port 1 to port
4 matches
Mail list logo