DEV Community

林子篆
林子篆

Posted on • Originally published at dannypsnl.github.io on

DPDK usertools: devbind

#dpdk #networking #workrecord

After compiling DPDK, load module and start our process. A common problem is we have no idea where is the NIC going :).

And DPDK actually provides some tools for these operations, one of them is dpdk-devbind.py. It located at $(DPDK_PROJECT)/usertools/dpdk-devbind.py

We can use it to get current status:

$ dpdk-devbind.py --status
# shorthand
$ dpdk-devbind.py -s
Enter fullscreen mode Exit fullscreen mode

Bind driver:

$ dpdk-devbind.py --bind e1000e 00:06.0
# shorthand
$ dpdk-devbind.py -b e1000e 00:06.0
# we also can use NIC name, but remember that a NIC could have no name
# only PCI would always existed.
$ dpdk-devbind.py -b igb_uio eth1
Enter fullscreen mode Exit fullscreen mode

Unbind driver:

$ dpdk-devbind.py --unbind 00:06.0
# shorthand
$ dpdk-devbind.py -u 00:06.0
# equal to
$ dpdk-devbind.py --bind none 00:06.0
Enter fullscreen mode Exit fullscreen mode

p.s. Remember that these operations requiring permission(sudo or what).

Just that, have fun!

Top comments (0)

Read next

estebanpiero profile image

AWS VPC Peering vs Transit Gateway: Which One Should You Use?

Esteban -

piotr_zarycki_fe062ceaa4c profile image

How to make http request without curl or wget in bash

Piotr Zarycki -

devsdaddy profile image

Developing a custom binary protocol for Node.js and WebSockets based applications with authorization via JWT

Devs Daddy -

stevenacoffman profile image

Browser Client to gRPC Server Routing options: Connect, gRPC-web, gRPC-gateway and more!

Steve Coffman -