Parav Pandit

rdmamap.GetRdmaCharDevices() from https://github.com/Mellanox/rdmamap will give list of desired devices, to map to container. Also, same device name can be used to setup rdma cgroup limits if needed available in OCI...

I will take look. Somehow didn't see the notification.

@simongu , plugin is migrated to https://hub.docker.com/r/rdma/k8s-rdma-sriov-dev-plugin/. Please use from there. You can also find a step-by-step document at https://community.mellanox.com/docs/DOC-3151

@yh-xu My suspect is SM config given that physical link is up

Hi @LucaPrete , ConnectX3 are not supported by the plugin. I recommend you to upgrade to ConnectX4 or 5. They bring lot of features that will be useful for rdma...

Hi @LucaPrete what functionality do you plan to run on ConnectX3? rdma, ethernet, dpdk, or part of it?

@LucaPrete, Connectx3 are pretty old now. Can you please talk to customer support as you need DPDK support in next step? We don't have strong plan to support DPDK mode....

@LucaPrete for PoC is fine to use ConnectX3. It requires some work, so some hacks should be done for PoC.

@zlwfrank container might not have IPC_LOCK capabilities. Refer to example here to add "IPC_LOCK" line at appropriate place. spec: restartPolicy: OnFailure containers: - image: mellanox/mlnx_ofed_linux-4.4-1.0.0.0-centos7.4 name: mofed-test-ctr securityContext: capabilities: add:...

@j0hnL, in sriov mode, each container gets its own sriov based accelerated netdev (non overlay netdev). This is auto configured by this device plugin already. if you are using shared...