Support multiple path records
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | RDMA/core: Rename rdma_route.num_paths field to num_pri_alt_pathsdrivers/ drivers/ include/ | +20 | 0 replies | |
| 2/4 | RDMA/cma: Multiple path records support with netlink channeldrivers/ drivers/ drivers/ +3 more | +231 | 6 replies | |
| 3/4 | RDMA/cm: Use SLID in the work completion as the DLID in responder sidedrivers/ | +7 | 0 replies | |
| 4/4 | RDMA/cm: Use DLID from inbound/outbound PathRecords as the datapath DLIDdrivers/ drivers/ include/ | +27 | 0 replies |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by.
| Patch | Mark Bloch |
|---|---|
| 1/4 | R-b |
| 2/4 | R-b |
| 3/4 | R-b |
| 4/4 | 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 0/4] Support multiple path records
From: Leon Romanovsky <[email protected]>
From Mark:
These patches allow IB core to receive multiple path records from user-space rdma netlink service.
Currently only one GMP PR is supported when doing a PR query. This means in a fabric with multiple subnets, when a packet goes out of the sender, it’s assigned with a LID to a router as its destination LID. The current solution selects a specific router per destination, means that there is no advanced routing from the sender towards the network.
This patchset supports to receive an inbound PR and an outbound PR along with the GMP PR. The LIDs in these 3 PRs can be used in this way:
1. GMP PR: used as the standard local/remote LIDs;
2. DLID of outbound PR: Used as the "dlid" field for outbound traffic;
3. DLID of inbound PR: Used as the "dlid" field for outbound traffic in responder side.
The inboundPR.dlid is passed to responder with the "primary_LID" filed in the ConnectRequest message.
With this, the user-space rdma netlink service can set special DLIDs in inbound/outbound PRs, to select specific routers for datapath between the 2 nodes.
The following cases were tested:
- New kernel with new netlink service that supports multiple path records;
- New kernel with old netlink service;
- Old kernel with new netlink service;
- Client side new kernel with new netlink service, server side with old kernel.
Thanks.
Mark Zhang (4):
RDMA/core: Rename rdma_route.num_paths field to num_pri_alt_paths RDMA/cma: Multiple path records support with netlink channel RDMA/cm: Use SLID in the work completion as the DLID in responder side RDMA/cm: Use DLID from inbound/outbound PathRecords as the datapath
DLID
drivers/infiniband/core/cm.c | 39 +++- drivers/infiniband/core/cma.c | 88 ++++++-- drivers/infiniband/core/sa_query.c | 235 +++++++++++++++------- drivers/infiniband/core/ucma.c | 10 +- drivers/infiniband/ulp/ipoib/ipoib_main.c | 2 +- drivers/infiniband/ulp/srp/ib_srp.c | 2 +- include/rdma/ib_cm.h | 2 + include/rdma/ib_sa.h | 3 +- include/rdma/rdma_cm.h | 13 +- 9 files changed, 284 insertions(+), 110 deletions(-)
Signature · 1 line
2.37.2