On Sun, Jul 08, 2018 at 01:24:36PM +0300, Leon Romanovsky wrote: > From: Leon Romanovsky <leonro@xxxxxxxxxxxx> > > >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 > IB: Enable uverbs_destroy_def_handler to be used by drivers I applied this one > Yishai Hadas (9): > net/mlx5: Add forward compatible support for the FTE match data > net/mlx5: Add support for flow table destination number > 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 The rest will need to be resent after the comments are addressed. Thanks, Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
