12/10/2022 19:59, Nicolas Chautru: > +Bind PF UIO driver(s) > +~~~~~~~~~~~~~~~~~~~~~ > + > +Install the DPDK igb_uio driver, bind it with the PF PCI device ID and use > +``lspci`` to confirm the PF device is under use by ``igb_uio`` DPDK UIO > driver.
igb_uio is not recommended. Please focus on VFIO first. > +The igb_uio driver may be bound to the PF PCI device using one of two methods > +for ACC200: > + > + > +1. PCI functions (physical or virtual, depending on the use case) can be > bound > +to the UIO driver by repeating this command for every function. > + > +.. code-block:: console > + > + cd <dpdk-top-level-directory> > + insmod ./build/kmod/igb_uio.ko > + echo "8086 57c0" > /sys/bus/pci/drivers/igb_uio/new_id > + lspci -vd8086:57c0 > + > + > +2. Another way to bind PF with DPDK UIO driver is by using the > ``dpdk-devbind.py`` tool > + > +.. code-block:: console > + > + cd <dpdk-top-level-directory> > + ./usertools/dpdk-devbind.py -b igb_uio 0000:f7:00.0 > + > +where the PCI device ID (example: 0000:f7:00.0) is obtained using lspci > -vd8086:57c0 This binding is not specific to the driver. It would be better to refer to the Linux guide instead of duplicating it again and again. > +In a similar way the PF may be bound with vfio-pci as any PCIe device. You could mention igb_uio here. Is there any advantage in using igb_uio?