dperf 啟動失敗 #435

tryagain2023 · 2024-03-28T09:54:12Z

tryagain2023
Mar 28, 2024

您好，我想使用dperf，但是啟動失敗了，已配置了大頁，也綁定了網卡，但是還是無法啟動，
環境是Ubuntu 22.04, 所用的DPDK版本ubunut內建的, 物理內存8G，網卡為intel i219
懇請幫忙看看是哪個地方沒設定好?

//// 所用的conf檔是改自test/performance/bandwith裡的

# cat server.conf 
mode                        server
tx_burst                    1024
cpu                         0
duration                    150s
payload_size                1400
keepalive                   1s
port                        0000:00:1f.6    192.168.31.50   192.168.31.200
client      192.168.31.200      1
server      192.168.31.50     1
listen 80 1

//// 執行結果

# ./dperf -c server.conf 
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 2048 kB hugepages reported
EAL: VFIO support initialized
EAL: pci_map_resource(): cannot map resource(17, 0x1180000000, 0x20000, 0x0): Operation not permitted ((nil))
EAL: Requested device 0000:00:1f.6 cannot be used
EAL: Bus (pci) probe failed.
not enough ports available: avail 0 require 1
port init fail
dpdk init fail

//// 配置大頁的設定

# grep -i linux  /boot/grub/grub.cfg 
linux	/boot/vmlinuz-5.15.0-43-generic root=UUID=xxxxxxxx-87e5-47e0-bf1d-xxxxxxxxxxxx ro net.ifnames=0 biosdevname=0 default_hugepagesz=1GB hugepagesz=1G hugepages=4 quiet splash $vt_handoff

# cat /proc/meminfo | grep -i huge
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
FileHugePages:         0 kB
HugePages_Total:       4
HugePages_Free:        3
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
Hugetlb:         4194304 kB

//// 已綁定網卡

# dpdk-devbind.py -s

Network devices using DPDK-compatible driver
============================================
0000:00:1f.6 'Ethernet Connection (2) I219-V 15b8' drv=igb_uio unused=e1000e,vfio-pci

Network devices using kernel driver
===================================
0000:01:00.0 'Device 94c0' if=eth0 drv=atlantic unused=igb_uio,vfio-pci *Active*

Answered by tryagain2023

Apr 10, 2024

您好，
.我將系統升級到ubuntu 23.10，也將dpdk 更新到23.11，
實驗1結果OK，但是實驗2 還是無法ping 或是arping。

.後來改用了虛擬機器，dperf cleint與server就可以互通了!除了改用虛擬網卡wmxnet3，所用的步驟方式都實體機器的一樣。

.以下分享虛擬機器上的的操作:

//// 虛擬機器設定，將e1000改成wmxnet3 , ubuntu 22.04
參考:
https://blog.csdn.net/m0_68678128/article/details/136356460

//// 配置 hugepages
#vi /etc/default/grub
GRUB_CMDLINE_LINUX="nopku transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=4 intel_iommu=on"

#update-grub

//// 以上重開機使其生效

////安裝DPDK等套件
#apt update
#apt install dpdk dpdk-dev dpdk-kmods-dkms
#apt install git net-tools

//// 編譯dperf

#git clone https://github.com/baidu/dperf
#cd dperf
#export PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig
#make

//// 綁定網卡

#ifconi…

View full answer

pengjianzhang · 2024-03-28T09:59:19Z

pengjianzhang
Mar 28, 2024
Maintainer

是用root运行吗？

2 replies

tryagain2023 Mar 28, 2024
Author

是的，是以root權限運行的。

pengjianzhang Mar 28, 2024
Maintainer

试下自己编译dpdk 23

pengjianzhang · 2024-03-28T14:08:01Z

pengjianzhang
Mar 28, 2024
Maintainer

参考大页配置
linux16 /boot/vmlinuz-xxxx nopku transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=4 intel_iommu=on

1 reply

tryagain2023 Mar 29, 2024
Author

感謝您百忙之中這麼晚還能回復訊息!謝謝!
按照您提供的訊息重新調整大頁的參數，看起來還是無法正常執行...

//// 由於改成linux16會無法開機，所以還是維持用linux

# grep 1G /boot/grub/grub.cfg 
	linux	/boot/vmlinuz-5.15.0-43-generic root=UUID=xxxxxxxx-87e4-47e0-bf1d-xxxxxxxx ro net.ifnames=0 biosdevname=0 nopku transparent_hugepage=never default_hugepagesz=1GB hugepagesz=1G hugepages=4 intel_iommu=on quiet splash $vt_handoff

# cat /proc/meminfo | grep -i huge
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
FileHugePages:         0 kB
HugePages_Total:       4
HugePages_Free:        4
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
Hugetlb:         4194304 kB

//// 執行結果

# ./dperf -c server.conf 
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 2048 kB hugepages reported
EAL: VFIO support initialized
EAL: pci_map_resource(): cannot map resource(17, 0x1180000000, 0x20000, 0x0): Operation not permitted ((nil))
EAL: Requested device 0000:00:1f.6 cannot be used
EAL: Bus (pci) probe failed.
not enough ports available: avail 0 require 1
port init fail
dpdk init fail

pengjianzhang · 2024-03-29T04:44:18Z

pengjianzhang
Mar 29, 2024
Maintainer

请参考

https://stackoverflow.com/questions/8213671/mmap-operation-not-permitted
https://stackoverflow.com/questions/6828548/legacy-code-mmap-zero-page-operation-not-permitted-where-should-i-start

4 replies

tryagain2023 Apr 1, 2024
Author

您好，當我把secure boot關閉之後，我執行了第一次結果看起來是不行的，
但是隔了幾分鐘後(中間什麼也沒做)，再執行一次結果訊息變得不一樣了，
感覺要跟client端做溝通了?

目前還再找第二台可用的機器來做cleint端。感謝您的建議。

第一次執行結果

# ./dperf -c server.conf 
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 2048 kB hugepages reported
EAL: VFIO support initialized
EAL: Probe PCI driver: net_e1000_em (8086:15b8) device: 0000:00:1f.6 (socket 0)
eth_em_start(): Unable to initialize the hardware
port start error: No such file or directory
start port fail
dpdk init fail

第二次執行結果

# ./dperf -c server.conf 
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 2048 kB hugepages reported
EAL: VFIO support initialized
EAL: Probe PCI driver: net_e1000_em (8086:15b8) device: 0000:00:1f.6 (socket 0)
socket allocation succeeded, memory size 0.01GB socket num 65535.
Error: bad gateway. dperf cannot find gateway's MAC address. Please check the link.

pengjianzhang Apr 1, 2024
Maintainer

启动成功了

pengjianzhang Apr 1, 2024
Maintainer

能不能写个文章，总结一下在ubuntu上如何运行dperf
我把文章链接挂在dperf.org上，供其他人参考

如果喜欢dperf，请加个star，谢谢

tryagain2023 Apr 1, 2024
Author

Star奉上.
等我找到一台可用的機器當作cleint，再驗證一次自己的安裝步驟，之後再把步驟貼上來。

謝謝

tryagain2023 · 2024-04-02T09:19:21Z

tryagain2023
Apr 2, 2024
Author

您好，我參考dperf.org的performance testing basic，測個bandwitch看看dperf是否能運作起來，
不過client端pktTx看起來有送出，server端的接收始終為零，不知是dperf的哪裡沒設定好?

環境:
server與client PC不透過switch直接用網路線串聯，在interface綁定之前有先試著設定IP，且確定彼此能ping通，
以ufw status確認防火牆雙方均為inactive的狀態。

//// server端設定

mode                        server
tx_burst                    128
cpu                         0
duration                    150s
payload_size                1400
keepalive                   1s
port                        0000:00:1f.6    192.168.31.50   192.168.31.200 88:d7:f6:57:c3:53
client      192.168.31.200      1
server      192.168.31.50     1
listen 80 1

//// server端過程的訊息

seconds 153                cpuUsage 0   
pktRx   0                  pktTx    0                  bitsRx   0                  bitsTx  0                  dropTx  0                 
tcpRx   0                  tcpTx    0                  udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    0                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    0                  finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   0                  finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  0                  skClose  0                  skCon    0                  skErr   0                 
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0                 

Total Numbers:
pktRx   0                  pktTx    2                  bitsRx   0                  bitsTx  672                dropTx  0                 
tcpRx   0                  tcpTx    0                  udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    2                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    0                  finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   0                  finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  0                  skClose  0                  skCon    0                  skErr   0                 
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0

//// cleint端設定

mode                        client
tx_burst                    128
launch_num                  10
cpu                         1 
payload_size                1400
duration                    120s
cps                         300
cc                          3000
keepalive                   1ms
port        0000:00:1f.6    192.168.31.200   192.168.31.50 88:d7:f6:57:c3:43
client      192.168.31.200      1
server      192.168.31.50     1
listen 80 5

//// cleint 端過程的訊息

seconds 153                cpuUsage 0   
pktRx   0                  pktTx    600                bitsRx   0                  bitsTx  297,600            dropTx  0                 
tcpRx   0                  tcpTx    600                udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    0                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    600                finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   600                finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  0                  skClose  300                skCon    1,200              skErr   300               
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0                 

Total Numbers:
pktRx   0                  pktTx    162,022            bitsRx   0                  bitsTx  80,362,592         dropTx  155,646           
tcpRx   0                  tcpTx    162,020            udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    2                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    162,020            finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   121,440            finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  40,580             skClose  39,680             skCon    900                skErr   39,680            
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0

0 replies

pengjianzhang · 2024-04-02T09:33:24Z

pengjianzhang
Apr 2, 2024
Maintainer

mode server
tx_burst 4
cpu 0
duration 1500s
payload_size 1400
keepalive 3s
port 0000:00:1f.6 192.168.31.50 192.168.31.200
client 192.168.31.200 1
server 192.168.31.50 1
listen 80 1

mode client
tx_burst 4
launch_num 10
cpu 1
payload_size 1400
duration 1000s
cc 100
keepalive 1ms
port 0000:00:1f.6 192.168.31.200 192.168.31.50
client 192.168.31.200 1
server 192.168.31.50 1
listen 80 1

16 replies

tryagain2023 Apr 8, 2024
Author

首先抱歉這麼晚才回訊息，

1.如果server端的config file 沒有配置MAC的話，會無法啟動，會出現"Error: bad gateway. dperf cannot find gateway's MAC address. Please check the link."

2.cleint 端無法 apring 到server端。因為 arping 會試圖使用上網用的interface，而非 dperf的interface。

3.另外，在client與server端，我都用ifconfig down 將上網的interface 先給disable，
再去啟動dperf，server端跟以前一樣過程的數據都是0，
client的數據跟以前有點不一樣，dropTx 都是0，而synRt與skErr過程中不斷出現紅底字體。

//// cleint 端過程的訊息

Total Numbers:
pktRx   0                  pktTx    4,002              bitsRx   0                  bitsTx  1,984,672          dropTx  0                 
tcpRx   0                  tcpTx    4,000              udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    2                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    4,000              finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   3,000              finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  1,000              skClose  1,000              skCon    0                  skErr   1,000             
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0

pengjianzhang Apr 8, 2024
Maintainer

dperf server用ARP没有找到client，需要检查一下网络的连通性。

实验1：

client, server上网卡都恢复原始状态
client上用dperf网卡（enp0s31f6）ping和arping derver上dperf网卡

实验2：

client上网卡恢复原始状态
server上启动dperf
1. client上用dperf网卡（enp0s31f6）ping和arping derver上dperf网卡

tryagain2023 Apr 8, 2024
Author

更正上述第3點，時間觀察久一點還是會出現dropTx。

//// cleint 端過程的訊息

Total Numbers:
pktRx   0                  pktTx    51,602             bitsRx   0                  bitsTx  25,594,272         dropTx  45,054            
tcpRx   0                  tcpTx    51,600             udpRx    0                  udpTx   0                 
arpRx   0                  arpTx    2                  icmpRx   0                  icmpTx  0                 
tosRx   0                  otherRx  0                  badRx    0                 
synRx   0                  synTx    51,600             finRx    0                  finTx   0                  rstRx   0          rstTx 0         
synRt   38,700             finRt    0                  ackRt    0                  pushRt  0                 
tcpDrop 0                  udpDrop  0                  ackDup   0                 
skOpen  12,900             skClose  12,800             skCon    100                skErr   12,800            
httpGet 0                  http2XX  0                  httpErr  0                 
ierrors 0                  oerrors  0                  imissed  0

tryagain2023 Apr 8, 2024
Author

實驗1:
client 端可以ping與arping 到server端。

client 端 log:

ifconfig
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.31.200  netmask 255.255.255.0  broadcast 192.168.31.255
        inet6 fe80::7974:e4fe:2af:d7e6  prefixlen 64  scopeid 0x20<link>
        ether 88:d7:f6:57:c3:53  txqueuelen 1000  (Ethernet)
        RX packets 116  bytes 24233 (24.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 273  bytes 44160 (44.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf200000-df220000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2894  bytes 212979 (212.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2894  bytes 212979 (212.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@PC2:/home/alpha# ping 192.168.31.50
PING 192.168.31.50 (192.168.31.50) 56(84) bytes of data.
64 bytes from 192.168.31.50: icmp_seq=1 ttl=64 time=0.615 ms
64 bytes from 192.168.31.50: icmp_seq=2 ttl=64 time=0.538 ms
^C
--- 192.168.31.50 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 0.538/0.576/0.615/0.038 ms
root@PC2:/home/alpha# arping 192.168.31.50
ARPING 192.168.31.50
60 bytes from 88:d7:f6:57:c3:43 (192.168.31.50): index=0 time=447.539 usec
60 bytes from 88:d7:f6:57:c3:43 (192.168.31.50): index=1 time=406.570 usec
60 bytes from 88:d7:f6:57:c3:43 (192.168.31.50): index=2 time=534.878 usec
60 bytes from 88:d7:f6:57:c3:43 (192.168.31.50): index=3 time=538.660 usec
^C
--- 192.168.31.50 statistics ---
4 packets transmitted, 4 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 0.407/0.482/0.539/0.057 ms

實驗2:

當server端的dperf帶起來後，cleint端就無法ping與arping到server端。

server端 log:

# ifconfig
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.31.50  netmask 255.255.255.0  broadcast 192.168.31.255
        inet6 fe80::a5bf:713e:beec:f40f  prefixlen 64  scopeid 0x20<link>
        ether 88:d7:f6:57:c3:43  txqueuelen 1000  (Ethernet)
        RX packets 8  bytes 930 (930.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 72  bytes 8652 (8.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf500000-df520000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 230  bytes 21947 (21.9 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 230  bytes 21947 (21.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@PC1:/home/alpha/D# modprobe uio
root@PC1:/home/alpha/D# modprobe igb_uio
root@PC1:/home/alpha/D# dpdk-devbind.py -b igb_uio eth1
Warning: routing table indicates that interface 0000:00:1f.6 is active. Not modifying
root@PC1:/home/alpha/D# ifconfig eth1 down
root@PC1:/home/alpha/D# dpdk-devbind.py -b igb_uio eth1
root@PC1:/home/alpha/D# dpdk-devbind.py -s

Network devices using DPDK-compatible driver
============================================
0000:00:1f.6 'Ethernet Connection (2) I219-V 15b8' drv=igb_uio unused=e1000e,vfio-pci

Network devices using kernel driver
===================================
0000:01:00.0 'Device 94c0' if=eth0 drv=atlantic unused=igb_uio,vfio-pci 

No 'Baseband' devices detected
==============================

No 'Crypto' devices detected
============================

No 'DMA' devices detected
=========================

No 'Eventdev' devices detected
==============================

No 'Mempool' devices detected
=============================

No 'Compress' devices detected
==============================

No 'Misc (rawdev)' devices detected
===================================

No 'Regex' devices detected
===========================
root@PC1:/home/alpha/D# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 335  bytes 29652 (29.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 335  bytes 29652 (29.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

client 端 log:

root@PC2:/home/alpha# ping 192.168.31.50
PING 192.168.31.50 (192.168.31.50) 56(84) bytes of data.
^C
--- 192.168.31.50 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8200ms

root@PC2:/home/alpha# arping 192.168.31.50
ARPING 192.168.31.50
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
Timeout
^C
--- 192.168.31.50 statistics ---
8 packets transmitted, 0 packets received, 100% unanswered (0 extra)

root@PC2:/home/alpha# ifconfig
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.31.200  netmask 255.255.255.0  broadcast 192.168.31.255
        inet6 fe80::7974:e4fe:2af:d7e6  prefixlen 64  scopeid 0x20<link>
        ether 88:d7:f6:57:c3:53  txqueuelen 1000  (Ethernet)
        RX packets 83  bytes 10770 (10.7 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 139  bytes 17670 (17.6 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf200000-df220000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5808  bytes 417025 (417.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5808  bytes 417025 (417.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pengjianzhang Apr 8, 2024
Maintainer

看起来是dperf或者DPDK的问题
你用DPDK自带的testpmd跑一下，看看是不是正常

pengjianzhang · 2024-04-08T05:02:27Z

pengjianzhang
Apr 8, 2024
Maintainer

用DPDK-23.11，intel i219是23.07才支持的

1 reply

tryagain2023 Apr 10, 2024
Author

您好，
.我將系統升級到ubuntu 23.10，也將dpdk 更新到23.11，
實驗1結果OK，但是實驗2 還是無法ping 或是arping。

.後來改用了虛擬機器，dperf cleint與server就可以互通了!除了改用虛擬網卡wmxnet3，所用的步驟方式都實體機器的一樣。

.以下分享虛擬機器上的的操作:

//// 虛擬機器設定，將e1000改成wmxnet3 , ubuntu 22.04
參考:
https://blog.csdn.net/m0_68678128/article/details/136356460

//// 配置 hugepages
#vi /etc/default/grub
GRUB_CMDLINE_LINUX="nopku transparent_hugepage=never default_hugepagesz=1G hugepagesz=1G hugepages=4 intel_iommu=on"

#update-grub

//// 以上重開機使其生效

////安裝DPDK等套件
#apt update
#apt install dpdk dpdk-dev dpdk-kmods-dkms
#apt install git net-tools

//// 編譯dperf

#git clone https://github.com/baidu/dperf
#cd dperf
#export PKG_CONFIG_PATH=/usr/lib/x86_64-linux-gnu/pkgconfig
#make

//// 綁定網卡

#ifconifg eno1 down

#modprobe uio
#modpeobe igb_uio

#dpdk-devbind.py -b igb_uio eno1
#dpdk-devbind.py -s

Answer selected by pengjianzhang

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

dperf 啟動失敗 #435

{{title}}

Replies: 6 comments 24 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

dperf 啟動失敗 #435

tryagain2023 Mar 28, 2024

Replies: 6 comments · 24 replies

pengjianzhang Mar 28, 2024 Maintainer

tryagain2023 Mar 28, 2024 Author

pengjianzhang Mar 28, 2024 Maintainer

pengjianzhang Mar 28, 2024 Maintainer

tryagain2023 Mar 29, 2024 Author

pengjianzhang Mar 29, 2024 Maintainer

tryagain2023 Apr 1, 2024 Author

pengjianzhang Apr 1, 2024 Maintainer

pengjianzhang Apr 1, 2024 Maintainer

tryagain2023 Apr 1, 2024 Author

tryagain2023 Apr 2, 2024 Author

pengjianzhang Apr 2, 2024 Maintainer

tryagain2023 Apr 8, 2024 Author

pengjianzhang Apr 8, 2024 Maintainer

tryagain2023 Apr 8, 2024 Author

tryagain2023 Apr 8, 2024 Author

pengjianzhang Apr 8, 2024 Maintainer

pengjianzhang Apr 8, 2024 Maintainer

tryagain2023 Apr 10, 2024 Author

tryagain2023
Mar 28, 2024

Replies: 6 comments 24 replies

pengjianzhang
Mar 28, 2024
Maintainer

tryagain2023 Mar 28, 2024
Author

pengjianzhang Mar 28, 2024
Maintainer

pengjianzhang
Mar 28, 2024
Maintainer

tryagain2023 Mar 29, 2024
Author

pengjianzhang
Mar 29, 2024
Maintainer

tryagain2023 Apr 1, 2024
Author

pengjianzhang Apr 1, 2024
Maintainer

pengjianzhang Apr 1, 2024
Maintainer

tryagain2023 Apr 1, 2024
Author

tryagain2023
Apr 2, 2024
Author

pengjianzhang
Apr 2, 2024
Maintainer

tryagain2023 Apr 8, 2024
Author

pengjianzhang Apr 8, 2024
Maintainer

tryagain2023 Apr 8, 2024
Author

tryagain2023 Apr 8, 2024
Author

pengjianzhang Apr 8, 2024
Maintainer

pengjianzhang
Apr 8, 2024
Maintainer

tryagain2023 Apr 10, 2024
Author