DPDK: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
[schwarzgerat](0) $ | [schwarzgerat](0) $ | ||
</pre> | </pre> | ||
After eliminating any routes associated with a device, we can bind it to a DPDK PMD: | |||
<pre> | |||
[schwarzgerat](0) $ sudo dpdk-devbind.py --bind=vfio-pci aq5 | |||
[schwarzgerat](0) $ dpdk-devbind.py --status | |||
Network devices using DPDK-compatible driver | |||
============================================ | |||
0000:44:00.0 'AQC111 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] 11b1' drv=vfio-pci unused=atlantic | |||
</pre> | |||
This has unbound the device from the <tt>atlantic</tt> driver (which can now be unloaded, if we wish). There is no longer any `aq5` interface, but an <tt>nlmon</tt> has shown up. | |||
==Secondary processes== | |||
Tools like <tt>dpdk-pdump</tt> and <tt>dpdk-proc-info</tt> are <i>secondary tools</i>--they require a primary tool to be running, and to have already configured the packet capture framework. | |||