linux-toradex.git/include/linux/mlx5/fs.h, branch v4.18

IB/mlx5: Add flow counters binding support

2018-06-02T04:35:32+00:00

Associates a counters with a flow when IB_FLOW_SPEC_ACTION_COUNT is part
of the flow specifications.

The counters user space placements of location and description (index,
description) pairs are passed as private data of the counters flow
specification.

Reviewed-by: Yishai Hadas 
Signed-off-by: Raed Salem 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe

net/mlx5: Export flow counter related API

2018-06-02T04:33:53+00:00

Exports counters API to be used in both IB and EN.

Reviewed-by: Yishai Hadas 
Signed-off-by: Raed Salem 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe

net/mlx5: Add destination e-switch owner

2018-05-17T21:17:34+00:00

The destination e-switch owner allows a rule in namespace of one e-switch
owner to point to a vport that is natively associated with another
e-switch owner.

Signed-off-by: Shahar Klein 
Reviewed-by: Or Gerlitz 
Reviewed-by: Roi Dayan 
Signed-off-by: Saeed Mahameed

net/mlx5: Add core support for vlan push/pop steering action

2018-03-26T20:47:13+00:00

Newer NICs (ConnectX-5 and onward) can apply vlan pop or push as an
action taking place during flow steering. Add the core bits for that.

Signed-off-by: Or Gerlitz 
Reviewed-by: Mark Bloch 
Signed-off-by: Saeed Mahameed

net/mlx5: Add flow-steering commands for FPGA IPSec implementation

2018-03-07T23:54:35+00:00

In order to add a context to the FPGA, we need to get both the software
transform context (which includes the keys, etc) and the
source/destination IPs (which are included in the steering
rule). Therefore, we register new set of firmware like commands for
the FPGA. Each time a rule is added, the steering core infrastructure
calls the FPGA command layer. If the rule is intended for the FPGA,
it combines the IPs information with the software transformation
context and creates the respective hardware transform.
Afterwards, it calls the standard steering command layer.

Signed-off-by: Aviad Yehezkel 
Signed-off-by: Saeed Mahameed

net/mlx5: Add empty egress namespace to flow steering core

2018-03-07T06:20:13+00:00

Currently, we don't support egress flow steering namespace in mlx5
flow steering core implementation. However, when we want to encrypt
a packet, we model it as a flow steering rule in the egress path.
To overcome this, we add an empty egress namespace to flow steering.
This namespace is initialized only when ipsec support exists.
In the future, this will grow to a full blown full steering
implementation, resembling the ingress path.

Signed-off-by: Matan Barak 
Signed-off-by: Aviad Yehezkel 
Signed-off-by: Saeed Mahameed

{net,IB}/mlx5: Add has_tag to mlx5_flow_act

2018-03-07T06:06:33+00:00

The has_tag member will indicate whether a tag action was specified
in flow specification.

A flow tag 0 = MLX5_FS_DEFAULT_FLOW_TAG is assumed a valid flow tag
that is currently used by mlx5 RDMA driver, whereas in HW flow_tag = 0
means that the user doesn't care about flow_tag.  HW always provide
a flow_tag = 0 if all flow tags requested on a specific flow are 0.

So we need a way (in the driver) to differentiate between a user really
requesting flow_tag = 0 and a user who does not care, in order to be
able to report conflicting flow tags on a specific flow.

Signed-off-by: Matan Barak 
Reviewed-by: Aviad Yehezkel 
Signed-off-by: Saeed Mahameed

net/mlx5: Separate ingress/egress namespaces for each vport

2017-12-28T22:43:52+00:00

Each vport has its own root flow table for the ACL flow tables and root
flow table is per namespace, therefore we should create a namespace for
each vport.

Fixes: efdc810ba39d ("net/mlx5: Flow steering, Add vport ACL support")
Signed-off-by: Gal Pressman 
Signed-off-by: Saeed Mahameed

net/mlx5: Use underlay QPN from the root name space

2017-05-14T10:33:45+00:00

Root flow table is dynamically changed by the underlying flow steering
layer, and IPoIB/ULPs have no idea what will be the root flow table in
the future, hence we need a dynamic infrastructure to move Underlay QPs
with the root flow table.

Fixes: b3ba51498bdd ("net/mlx5: Refactor create flow table method to accept underlay QP")
Signed-off-by: Erez Shitrit 
Signed-off-by: Maor Gottlieb 
Signed-off-by: Yishai Hadas 
Signed-off-by: Saeed Mahameed

net/mlx5: Refactor create flow table method to accept underlay QP

2017-04-17T15:08:29+00:00

IB flow tables need the underlay qp to perform flow steering.
Here we change the API of the flow tables creation to accept the
underlay QP number as a parameter in order to support IB (IPoIB) flow
steering.

Signed-off-by: Erez Shitrit 
Signed-off-by: Saeed Mahameed 
Signed-off-by: David S. Miller