linux.git/include/linux/mlx5/fs.h, branch v4.20-rc2

net/mlx5: Add a no-append flow insertion mode

2018-10-17T21:18:50+00:00

If no-append flag is set, we will add a new FTE, instead of appending
the actions of the inserted rule when the same match already exists.

While here, move the has_flow_tag boolean indicator to be a flag too.

This patch doesn't change any functionality.

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

net/mlx5: Split FDB fast path prio to multiple namespaces

2018-10-17T21:18:16+00:00

Towards supporting multi-chains and priorities, split the FDB fast path
to multiple namespaces (sub namespaces), each with multiple priorities.

This patch adds a new flow steering type, FS_TYPE_PRIO_CHAINS, which is
like current FS_TYPE_PRIO, but may contain only namespaces, and those
will be in parallel to one another in terms of managing of the flow
tables connections inside them. Meaning, while searching for the next
or previous flow table to connect for a new table inside such namespace
we skip the parallel namespaces in the same level under the
FS_TYPE_PRIO_CHAINS prio we originated from.

We use this new type for splitting the fast path prio into multiple
parallel namespaces, each containing normal prios.
The prios inside them (and their tables) will be connected to one
another, but not from one parallel namespace to another, instead the
last prio in each namespace will be connected to the next prio in
the containing FDB namespace, which is the slow path prio.

Signed-off-by: Paul Blakey 
Acked-by: Or Gerlitz 
Signed-off-by: Saeed Mahameed

net/mlx5: Use flow counter IDs and not the wrapping cache object

2018-10-17T21:15:48+00:00

Currently, when a flow rule is created using the FS core layer, the caller
has to pass the entire flow counter object and not just the counter HW
handle (ID). This requires both the FS core and the caller to have
knowledge about the inner implementation of the FS layer flow counters
cache and limits the possible users.

Move to use the counter ID across the place when dealing with flows.

Doing this decoupling, now can we privatize the inner implementation
of the flow counters.

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

net/mlx5: E-Switch, Get counters for offloaded flows from callers

2018-10-17T21:15:48+00:00

There's no real reason for the e-switch logic to manage the creation of
counters for offloaded flows. The API already has the directive for the
caller to denote they want to attach a counter to the created flow.
As such, we go and move the management of flow counters to the mlx5e
tc offload logic. This also lets us remove an inelegant interface where
the FS layer had to provide a way to retrieve a counter from a flow rule.

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

net/mlx5: Export packet reformat alloc/dealloc functions

2018-09-05T05:11:26+00:00

This will allow for the RDMA side to allocate packet reformat context.

Signed-off-by: Mark Bloch 
Reviewed-by: Saeed Mahameed 
Signed-off-by: Leon Romanovsky

{net, RDMA}/mlx5: Rename encap to reformat packet

2018-09-05T05:10:59+00:00

Renames all encap mlx5_{core,ib} code to use the new naming of packet
reformat. This change doesn't introduce any function change and is
needed to properly reflect the operation being done by this action.
For example not only can we encapsulate a packet, but also decapsulate it.

Signed-off-by: Mark Bloch 
Reviewed-by: Saeed Mahameed 
Signed-off-by: Leon Romanovsky

net/mlx5: Break encap/decap into two separated flow table creation flags

2018-09-05T04:58:00+00:00

Today we are able to attach encap and decap actions only to the FDB. In
preparation to enable those actions on the NIC flow tables, break the
single flag into two. Those flags control whatever a decap or encap
operations can be attached to the flow table created. For FDB, if
encapsulation is required, we set both of them.

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

net/mlx5: Export modify header alloc/dealloc functions

2018-09-05T04:56:40+00:00

Those functions will be used by the RDMA side to create modify header
actions to be attached to flow steering rules via verbs.

Signed-off-by: Mark Bloch 
Reviewed-by: Saeed Mahameed 
Signed-off-by: Leon Romanovsky

Merge branch 'linus/master' into rdma.git for-next

2018-08-16T20:21:29+00:00

rdma.git merge resolution for the 4.19 merge window

Conflicts:
 drivers/infiniband/core/rdma_core.c
   - Use the rdma code and revise with the new spelling for
     atomic_fetch_add_unless
 drivers/nvme/host/rdma.c
   - Replace max_sge with max_send_sge in new blk code
 drivers/nvme/target/rdma.c
   - Use the blk code and revise to use NULL for ib_post_recv when
     appropriate
   - Replace max_sge with max_recv_sge in new blk code
 net/rds/ib_send.c
   - Use the net code and revise to use NULL for ib_post_recv when
     appropriate

Signed-off-by: Jason Gunthorpe

net/mlx5: Improve argument name for add flow API

2018-08-13T19:50:17+00:00

The last argument to mlx5_add_flow_rules passes the number of
destinations in the struct pointed to by the dest arg. Change the name
to better reflect this fact.

Signed-off-by: Eli Cohen 
Reviewed-by: Or Gerlitz 
Signed-off-by: Saeed Mahameed