All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1164] iperf3 traffic stalls when using memif driver to interconnect l2fwd in zero-copy mode with test-pmd app
Date: Thu, 23 Feb 2023 12:33:23 +0000	[thread overview]
Message-ID: <bug-1164-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 3365 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1164

            Bug ID: 1164
           Summary: iperf3 traffic stalls when using memif driver to
                    interconnect l2fwd in zero-copy mode with test-pmd app
           Product: DPDK
           Version: 22.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: srinidpdk@gmail.com
  Target Milestone: ---

Created attachment 240
  --> https://bugs.dpdk.org/attachment.cgi?id=240&action=edit
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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 5392 bytes --]

                 reply	other threads:[~2023-02-23 12:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1164-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.