Enable flow steering on IPoIB UD QP
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest6 patches 6 repliesIn review
- v16 patches 0 repliesSuperseded
Changes in v2 from the cover letter
* Use 'source_qpn' as part of QP creation without mandating association of an overlay with underlay QP.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | IB/core: Enable QP creation with a given source QP numberinclude/ | +2 | 0 replies | |
| 2/6 | IB/uverbs: Enable QP creation with a given source QP numberdrivers/ include/ | +15 | 0 replies | |
| 3/6 | IB/mlx5: Add support for QP with a given source QPNdrivers/ drivers/ | +59 | 5 replies | |
| 4/6 | IB/mlx5: Add multicast flow steering support for underlay QPdrivers/ | +31 | 0 replies | |
| 5/6 | net/mlx5: Report enhanced capabilities for IPoIBdrivers/ include/ | +11 | 0 replies | |
| 6/6 | IB/mlx5: Report RX checksum capabilities for IPoIBdrivers/ | +4 | 0 replies |
Reviews trailers per patch
All 6 patches have a Reviewed-by or Acked-by.
| Patch | Maor Gottlieb |
|---|---|
| 1/6 | R-b |
| 2/6 | R-b |
| 3/6 | R-b |
| 4/6 | R-b |
| 5/6 | R-b |
| 6/6 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH rdma-next V2 0/6] Enable flow steering on IPoIB UD QP
Hi,
This is v2 of patch set from Yishai,
Changelog:
v1->v2:
* Use 'source_qpn' as part of QP creation without mandating association of an overlay with underlay QP.
v0->v1:
* Improved commit message
----
Quoted 1 line
From Yishai:
Enable accelerating IPoIB traffic from user applications
This series comes to allow user space applications to accelerate send and receive traffic which is typically handled by IPoIB ULP. On the receive flow, the user space application will use flow steering rules to direct the ingress IPoIB UD QP traffic to its own user space UD QP. On the send flow, the user space application will send from its own UD QP with UD AH, while the packet on the wire will have the source QPN of the IPoIB UD QP, which is the network interface advertised L2 hardware address.
This will be achieved by extending QP creation of IB UD QP to get the source QP number of the matching IPoIB UD QP.
In order to create such a UD QP needs to provide the source QPN of the IPoIB network interface.
The QPN should be achieved by using some networking tool as of ifconfig, ip link show on the associated interface. For example, when IPoIB is used, the QPN is the value of 3 bytes from the hardware address starting after the first byte as defined by rfc4391 [1]
Current mlx5 driver implements this API for the IPoIB ULP.
Thanks
[1] https://tools.ietf.org/html/rfc4391#page-11
---
Available in the "topic/underlay_qp_v2" topic branch of this git repo:git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
Or for browsing:
https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=topic/underlay_qp_v2
Possible merge conflicts resolution is available in:
https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=testing/queue-next
Yishai Hadas (6):
IB/core: Enable QP creation with a given source QP number IB/uverbs: Enable QP creation with a given source QP number IB/mlx5: Add support for QP with a given source QPN IB/mlx5: Add multicast flow steering support for underlay QP net/mlx5: Report enhanced capabilities for IPoIB IB/mlx5: Report RX checksum capabilities for IPoIB
drivers/infiniband/core/uverbs_cmd.c | 17 +++++-- drivers/infiniband/hw/mlx5/main.c | 47 +++++++++++++----- drivers/infiniband/hw/mlx5/mlx5_ib.h | 2 + drivers/infiniband/hw/mlx5/qp.c | 72 ++++++++++++++++++++++------ drivers/net/ethernet/mellanox/mlx5/core/fw.c | 6 +++ include/linux/mlx5/device.h | 6 ++- include/rdma/ib_verbs.h | 2 + include/uapi/rdma/ib_user_verbs.h | 2 +- 8 files changed, 122 insertions(+), 32 deletions(-)
--
2.12.2
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html