Bug 1164 - iperf3 traffic stalls when using memif driver to interconnect l2fwd in zero-copy mode with test-pmd app
Summary: iperf3 traffic stalls when using memif driver to interconnect l2fwd in zero-c...
Status: UNCONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: ethdev (show other bugs)
Version: 22.11
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Jakub Grajciar
URL:
Depends on:
Blocks:
 
Reported: 2023-02-23 13:33 CET by Srini
Modified: 2023-04-03 08:53 CEST (History)
2 users (show)



Attachments
Topology (5.17 KB, image/png)
2023-02-23 13:33 CET, Srini
Details

Description Srini 2023-02-23 13:33:23 CET
Created attachment 240 [details]
Topology

Traffic stalls when running iperf3 traffic between two ports of test-pmd which are looped back using l2wd via memif in zero-copy mode. The same test works fine if zero-copy mode is disabled in l2fwd app.


Topology used: (attached)

test-pmd: arguments

./dpdk-testpmd -m 380 -l 6-8  --base-virtaddr 0x100000000 --huge-dir /mnt/huge1 --vdev 'net_memif0,role=server,socket-abstract=no,id=1,socket=/tmp/memif0.sock' --vdev 'net_memif1,role=server,socket-abstract=no,id=1,socket=/tmp/memif1.sock' --log-level=8 --log-level user1:8 --log-level user2:8 -- --nb-cores=2 --txd=1024 --rxd=2048  -i

test-pmd: config

set fwd io
set portlist 0,2,1,3
start

l2fwd: arguments

./dpdk-l2fwd -l 4-5  --proc-type=auto  --no-pci --single-file-segments --vdev 'net_memif0,role=client,socket=/tmp/memif0.sock,socket-abstract=no,id=1,zero-copy=yes' --vdev 'net_memif1,role=client,socket=/tmp/memif1.sock,socket-abstract=no,id=1,zero-copy=yes' --file-prefix=container --log-level pmd.net.memif:8 -- -p 0x3 --no-mac-updating


[test@localhost src]$ pwd
/home/test/source/iperf-3.7/src
[test@localhost src]$ ./iperf3 -c 120.0.0.10 -B 120.0.0.20 -M 1000  -t 2000
Connecting to host 120.0.0.10, port 5201
[  5] local 120.0.0.20 port 50901 connected to 120.0.0.10 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  45.5 MBytes   382 Mbits/sec  164   20.3 KBytes
[  5]   1.00-2.00   sec  16.7 MBytes   140 Mbits/sec   78   12.5 KBytes
[  5]   2.00-3.00   sec  29.4 MBytes   247 Mbits/sec  136   20.3 KBytes
[  5]   3.00-4.00   sec  17.4 MBytes   146 Mbits/sec  128   9.65 KBytes
[  5]   4.00-5.00   sec  22.9 MBytes   192 Mbits/sec  103   29.9 KBytes
[  5]   5.00-6.00   sec  13.2 MBytes   111 Mbits/sec   68   23.2 KBytes
[  5]   6.00-7.00   sec  39.2 MBytes   329 Mbits/sec  159   7.72 KBytes
[  5]   7.00-8.00   sec  11.5 MBytes  96.5 Mbits/sec   47   19.3 KBytes
[  5]   8.00-9.00   sec  45.1 MBytes   378 Mbits/sec  146   10.6 KBytes
[  5]   9.00-10.00  sec  12.0 MBytes   101 Mbits/sec   74   15.4 KBytes
[  5]  10.00-11.00  sec  34.9 MBytes   293 Mbits/sec  130   4.82 KBytes
[  5]  11.00-12.00  sec  1.74 MBytes  14.6 Mbits/sec    9    988 Bytes
[  5]  12.00-13.00  sec  0.00 Bytes  0.00 bits/sec    1    988 Bytes
[  5]  13.00-14.00  sec  0.00 Bytes  0.00 bits/sec    0    988 Bytes
[  5]  14.00-15.00  sec  0.00 Bytes  0.00 bits/sec    1    988 Bytes
[  5]  15.00-16.00  sec  0.00 Bytes  0.00 bits/sec    0    988 Bytes
[  5]  16.00-17.00  sec  0.00 Bytes  0.00 bits/sec    0    988 Bytes
^C[  5]  17.00-17.68  sec  0.00 Bytes  0.00 bits/sec    1    988 Bytes

Note You need to log in before you can comment on or make changes to this bug.