Support mlx5 flow steering with RAW data
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest9 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/9 | net/mlx5: Add forward compatible support for the FTE match datadrivers/ | +1 | 0 replies | |
| 2/9 | net/mlx5: Add support for flow table destination numberdrivers/ drivers/ drivers/ +2 more | +22 | 2 replies | |
| 3/9 | IB: Enable uverbs_destroy_def_handler to be used by driversdrivers/ drivers/ drivers/ +1 more | +6 | 0 replies | |
| 4/9 | IB/mlx5: Introduce flow steering matcher objectdrivers/ drivers/ drivers/ +1 more | +176 | 3 replies | |
| 5/9 | IB: Consider ib_flow creation by the KABI infrastructuredrivers/ drivers/ include/ | +8 | 0 replies | |
| 6/9 | IB/mlx5: Introduce vendor create and destroy flow methodsdrivers/ drivers/ drivers/ +4 more | +202 | 2 replies | |
| 7/9 | IB/mlx5: Support adding flow steering rule by raw datadrivers/ drivers/ | +201 | 0 replies | |
| 8/9 | IB/mlx5: Add support for a flow table destinationdrivers/ | +8 | 0 replies | |
| 9/9 | IB/mlx5: Expose vendor flow treesdrivers/ drivers/ drivers/ | +15 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH rdma-next 0/9] Support mlx5 flow steering with RAW data
From: Leon Romanovsky <[email protected]>
Quoted 1 line
From Yishai:
This series introduces vendor create and destroy flow methods on the uverbs flow object by using the KABI infra-structure.
It's done in a way that enables the driver to get its specific device attributes in a raw data to match its underlay specification while still using the generic ib_flow object for cleanup and code sharing.
In addition, a specific mlx5 matcher object and its create/destroy methods were introduced. This object matches the underlay flow steering mask specification and is used as part of mlx5 create flow input data.
This series supports IB_QP/TIR as its flow steering destination as applicable today via the ib_create_flow API, however, it adds also an option to work with DEVX object which its destination can be both TIR and flow table.
Few changes were done in the mlx5 core layer to support forward compatible for the device specification raw data and to support flow table when the DEVX destination is used.
As part of this series the default IB destroy handler (i.e. uverbs_destroy_def_handler()) was exposed from IB core to be used by the drivers and existing code was refactored to use it.
Thanks
Yishai Hadas (9):
net/mlx5: Add forward compatible support for the FTE match data net/mlx5: Add support for flow table destination number
IB: Enable uverbs_destroy_def_handler to be used by drivers IB/mlx5: Introduce flow steering matcher object
IB: Consider ib_flow creation by the KABI infrastructure IB/mlx5: Introduce vendor create and destroy flow methods IB/mlx5: Support adding flow steering rule by raw data IB/mlx5: Add support for a flow table destination IB/mlx5: Expose vendor flow trees
drivers/infiniband/core/uverbs.h | 3 - drivers/infiniband/core/uverbs_cmd.c | 4 + drivers/infiniband/core/uverbs_std_types.c | 6 +- drivers/infiniband/hw/mlx5/Makefile | 1 + drivers/infiniband/hw/mlx5/devx.c | 40 ++-- drivers/infiniband/hw/mlx5/flow.c | 249 +++++++++++++++++++++ drivers/infiniband/hw/mlx5/main.c | 230 +++++++++++++++++-- drivers/infiniband/hw/mlx5/mlx5_ib.h | 31 +++ .../mellanox/mlx5/core/diag/fs_tracepoint.c | 3 + drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c | 21 +- drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 81 +------ include/linux/mlx5/fs.h | 1 + include/linux/mlx5/mlx5_ifc.h | 1 + include/rdma/ib_verbs.h | 18 ++ include/rdma/uverbs_named_ioctl.h | 29 ++- include/uapi/rdma/mlx5_user_ioctl_cmds.h | 50 ++++- 16 files changed, 633 insertions(+), 135 deletions(-) create mode 100644 drivers/infiniband/hw/mlx5/flow.c