net/mlx5: Support extended destination format in flow steering command
Update the flow steering command formatting according to the extended destination API. Note that the FW dictates that multi destination FTEs that involve at least one encap must use the extended destination format, while single destination ones must use the legacy format. Using extended destination format requires FW support. Check for its capabilities and return error if not supported. Signed-off-by: Eli Britstein <elibr@mellanox.com> Reviewed-by: Or Gerlitz <ogerlitz@mellanox.com> Reviewed-by: Oz Shlomo <ozsh@mellanox.com> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
This commit is contained in:

committed by
Saeed Mahameed

parent
aa39c2c0e4
commit
a2c6162b12
@@ -88,6 +88,7 @@ struct mlx5_flow_spec {
|
||||
|
||||
enum {
|
||||
MLX5_FLOW_DEST_VPORT_VHCA_ID = BIT(0),
|
||||
MLX5_FLOW_DEST_VPORT_REFORMAT_ID = BIT(1),
|
||||
};
|
||||
|
||||
struct mlx5_flow_destination {
|
||||
@@ -100,6 +101,7 @@ struct mlx5_flow_destination {
|
||||
struct {
|
||||
u16 num;
|
||||
u16 vhca_id;
|
||||
u32 reformat_id;
|
||||
u8 flags;
|
||||
} vport;
|
||||
};
|
||||
|
Reference in New Issue
Block a user