linux-toradex.git/include/uapi/rdma, branch v5.9-rc7

RDMA/efa: User/kernel compatibility handshake mechanism

2020-07-29T12:23:40+00:00

Introduce a mechanism that performs an handshake between the userspace
provider and kernel driver which verifies that the user supports all
required features in order to operate correctly.

The handshake verifies the needed functionality by comparing the reported
device caps and the provider caps. If the device reports a non-zero
capability the appropriate comp mask is required from the userspace
provider in order to allocate the context.

Link: https://lore.kernel.org/r/20200722140312.3651-4-galpress@amazon.com
Reviewed-by: Shadi Ammouri 
Reviewed-by: Yossi Leybovich 
Signed-off-by: Gal Pressman 
Signed-off-by: Jason Gunthorpe

RDMA/efa: Expose minimum SQ size

2020-07-29T12:23:39+00:00

The device reports the minimum SQ size required for creation.

This patch queries the min SQ size and reports it back to the userspace
library.

Link: https://lore.kernel.org/r/20200722140312.3651-3-galpress@amazon.com
Reviewed-by: Firas JahJah 
Reviewed-by: Shadi Ammouri 
Signed-off-by: Gal Pressman 
Signed-off-by: Jason Gunthorpe

RDMA/efa: Expose maximum TX doorbell batch

2020-07-29T12:23:39+00:00

The device reports the maximum number of bytes to be written before
ringing the doorbell (zero means unlimited).

This patch queries the max batch size and reports it back to the userspace
library.

Link: https://lore.kernel.org/r/20200722140312.3651-2-galpress@amazon.com
Reviewed-by: Daniel Kranzdorf 
Reviewed-by: Firas JahJah 
Signed-off-by: Gal Pressman 
Signed-off-by: Jason Gunthorpe

RDMA/mlx5: Fix typo in enum name

2020-07-24T20:02:15+00:00

Nnothing uses the enum name, so this is harmless.

Fixes: 322694412400 ("IB/mlx5: Introduce driver create and destroy flow methods")
Link: https://lore.kernel.org/r/20200724084112.GC31930@amd
Signed-off-by: Pavel Machek (CIP) 
Signed-off-by: Jason Gunthorpe

RDMA: rdma_user_ioctl.h: fix a duplicated word + clarify

2020-07-20T19:42:08+00:00

Change the repeated word "it" in a comment to "it to".
Also insert a dash in the sentence to add clarity.

Link: https://lore.kernel.org/r/20200719003220.21250-1-rdunlap@infradead.org
Signed-off-by: Randy Dunlap 
Signed-off-by: Jason Gunthorpe

RDMA/qedr: Add EDPM max size to alloc ucontext response

2020-07-16T19:01:55+00:00

User space should receive the maximum edpm size from kernel driver,
similar to other edpm/ldpm related limits.  Add an additional parameter to
the alloc_ucontext_resp structure for the edpm maximum size.

In addition, pass an indication from user-space to kernel
(and not just kernel to user) that the DPM sizes are supported.

This is for supporting backward-forward compatibility between driver and
lib for everything related to DPM transaction and limit sizes.

This should have been part of commit mentioned in Fixes tag.

Link: https://lore.kernel.org/r/20200707063100.3811-3-michal.kalderon@marvell.com
Fixes: 93a3d05f9d68 ("RDMA/qedr: Add kernel capability flags for dpm enabled mode")
Signed-off-by: Ariel Elior 
Signed-off-by: Michal Kalderon 
Signed-off-by: Jason Gunthorpe

RDMA/qedr: Add EDPM mode type for user-fw compatibility

2020-07-16T19:01:55+00:00

In older FW versions the completion flag was treated as the ack flag in
edpm messages.  commit ff937b916eb6 ("qed: Add EDPM mode type for user-fw
compatibility") exposed the FW option of setting which mode the QP is in
by adding a flag to the qedr <-> qed API.

This patch adds the qedr <-> libqedr interface so that the libqedr can set
the flag appropriately and qedr can pass it down to FW.  Flag is added for
backward compatibility with libqedr.

For older libs, this flag didn't exist and therefore set to zero.

Fixes: ac1b36e55a51 ("qedr: Add support for user context verbs")
Link: https://lore.kernel.org/r/20200707063100.3811-2-michal.kalderon@marvell.com
Signed-off-by: Yuval Bason 
Signed-off-by: Michal Kalderon 
Signed-off-by: Jason Gunthorpe

RDMA/counter: Add PID category support in auto mode

2020-07-10T19:50:53+00:00

With the "PID" category QPs have same PID will be bound to same counter;
If this category is not set then QPs have different PIDs will be bound
to same counter.

This is implemented for 2 reasons:
1. The counter is a limited resource, while there may be dozens of
   applications, each of which creates several types of QPs, which means
   it may doesn't have enough counter.
2. The system administrator needs all QPs created by all applications
   with same type bound to one counter.

The counter name and PID is only make sense when "PID" category are
configured.

This category can also be used in combine with others, e.g. QP type.

Link: https://lore.kernel.org/r/20200702082933.424537-2-leon@kernel.org
Signed-off-by: Mark Zhang 
Reviewed-by: Maor Gottlieb 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe

IB/uverbs: Expose UAPI to query MR

2020-07-06T22:50:34+00:00

Expose UAPI to query MR, this will let user space application that
didn't allocate the MR but has access to by owning the matching command
FD to retrieve its information.

Link: https://lore.kernel.org/r/20200630093916.332097-8-leon@kernel.org
Signed-off-by: Yishai Hadas 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe

RDMA/mlx5: Introduce UAPI to query PD attributes

2020-07-06T22:50:34+00:00

Introduce UAPI to query PD attributes, this can be used to retrieve PD
attributes by having the PD handle of the created one and owning the
command FD for the ucontxet.

Link: https://lore.kernel.org/r/20200630093916.332097-7-leon@kernel.org
Signed-off-by: Yishai Hadas 
Signed-off-by: Leon Romanovsky 
Signed-off-by: Jason Gunthorpe