Hi,
This patchset contains rdma network namespace issue fixes.
Steps to reproduce issues as follow:
1. Bringup container with option '-net=none'
docker run --privileged --net=none -v /dev/infiniband:/dev/infiniband \
-itd --name=container1 roce
2. Add PF or VF to container with pipework
VF_NAME=enP8p1s0f0
pipework --direct-phys $VF_NAME container1 192.168.1.10/24
3. ib_send_lat test with TCP connect or RDMA-CM connect.
1) ModeA: TCP connect
rdma_cm QPs : OFF
Data ex. method : Ethernet
Server: ib_send_lat -d bnxt_re0 -x 3
Client: ib_send_lat -d bnxt_re0 -x 3 192.168.1.10
2) ModeB: IB connect
rdma_cm QPs : OFF
Data ex. method : rdma_cm
Server: ib_send_lat -d bnxt_re0 -x 3 -z
Client: ib_send_lat -d bnxt_re0 -x 3 192.168.1.10 -z
3) ModeC: IB connect
rdma_cm QPs : ON
Data ex. method : rdma_cm
Server: ib_send_lat -d bnxt_re0 -x 3 -R
Client: ib_send_lat -d bnxt_re0 -x 3 192.168.1.10 -R
Without patch #1, it will fail to get ip_route_output_key because it still
uses init_net namespace.
Without patch #2, it cannot setup ib connection.
This patchset has been tested on Broadcom SST100 board.
Qingmin Liu (2):
infiniband: core: fix network namespace issue with container -net=none
infiniband: Fix cma_id_from_event net dev missing issue
drivers/infiniband/core/addr.c | 2 +-
drivers/infiniband/core/cma.c | 14 ++++++++++----
2 files changed, 11 insertions(+), 5 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
