-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dpdk driver with containers #36
Comments
i am facing the same |
Me too, I have some difficulties sorting this thing out. Usually you know that the order of plugins is retained as net0, net1..., but here we dont have any visible kernel devices. Under /dev/vfio I can find some number, and if I run priviliged mode, I'll se all the vfio sriov on the blade. I need to have a mapping between netX and pci-addr at least. I'm thinking of using the network annotation for the pod, to put the data there. or if I in someway can create a file in the container from the cni plugin??? |
We are working in SRIOV network device plugin, which uses SRIOV CNI. The plan is to provide strong isolation of the device. The intermediate solution is available in the DPDK CNI. |
The problem for me is that if I have more then one network (via multus) there is no way of finding out the which network (according to pod spec. ie. net0, net1 ...), because all I can see is a bunch of pci devices under vfio-pci. What I done is to add the creation of a dummy eth device, to carry info about mac address and pci addr vs the assigned dev name: / # ip -d link show |
HI ,
i have deployed the 2 containers with dpdk driver but i am unable to find out which device is used by whch container ,
can you just help me to which dpdk driver i was bounded to as in dpdk tools i am seeing both the devices intact to our dpdk driver.
The text was updated successfully, but these errors were encountered: