diff options
| author | Parav Pandit <[email protected]> | 2018-03-21 17:16:35 +0200 |
|---|---|---|
| committer | Jason Gunthorpe <[email protected]> | 2018-03-23 10:58:05 -0600 |
| commit | 114cc9c4b18232452f7dcc8bb3e5749f8d9a6837 (patch) | |
| tree | 51d182911abb1814a0ba2644affef379ec30ed27 /tools/perf/scripts/python | |
| parent | 98f1f4e0ed26c97a697f1e007416acbc18f4a8a9 (diff) | |
IB/cma: Resolve route only while receiving CM requests
Currently CM request for RoCE follows following flow.
rdma_create_id()
rdma_resolve_addr()
rdma_resolve_route()
For RC QPs:
rdma_connect()
->cma_connect_ib()
->ib_send_cm_req()
->cm_init_av_by_path()
->ib_init_ah_attr_from_path()
For UD QPs:
rdma_connect()
->cma_resolve_ib_udp()
->ib_send_cm_sidr_req()
->cm_init_av_by_path()
->ib_init_ah_attr_from_path()
In both the flows, route is already resolved before sending CM requests.
Therefore, code is refactored to avoid resolving route second time in
ib_cm layer.
ib_init_ah_attr_from_path() is extended to resolve route when it is not
yet resolved for RoCE link layer. This is achieved by caller setting
route_resolved field in path record whenever it has route already
resolved.
Signed-off-by: Parav Pandit <[email protected]>
Signed-off-by: Leon Romanovsky <[email protected]>
Signed-off-by: Jason Gunthorpe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions