From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1825] The DPDK memif driver fails to connect a second zero-copy client port from the same process, logging an "mmap failed: No such device" error.
Date: Mon, 10 Nov 2025 06:50:38 +0000 [thread overview]
Message-ID: <bug-1825-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1825
Bug ID: 1825
Summary: The DPDK memif driver fails to connect a second
zero-copy client port from the same process, logging
an "mmap failed: No such device" error.
Product: DPDK
Version: 23.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: staryyuuwx@gmail.com
Target Milestone: ---
Linux localhost 5.10.0-136.12.0.86.h1032.eulerosv2r12.aarch64 #1 SMP Wed Jun 28
18:34:50 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux
1. start two server memifs
./dpdk-testpmd -l 1-2 --file-prefix=pmd1
--vdev=net_memif0,socket=/run/memif_wx0,role=server
--vdev=net_memif1,socket=/run/memif_wx1,role=server -- -i
2. start one client memif
./dpdk-testpmd -l 3-4 -m 4096 --file-prefix=pmd2
--vdev=net_memif0,socket=/run/memif_wx0,role=client,zero-copy=yes
--single-file-segments -- -i
port 0 is up
testpmd> show port info 0
********************* Infos for port 0 *********************
MAC address: 72:5C:61:5A:E9:75
Device name: net_memif0
Driver name: net_memif
Firmware-version: not available
Devargs: socket=/run/memif_wx0,role=client,zero-copy=yes
Connect to socket: 0
memory allocation on the socket: 0
Link status: up
Link speed: 100 Gbps
Link duplex: full-duplex
......
3. add and start 2nd client memif, print "mmap failed: No such device"
client:
testpmd> port attach net_memif1,socket=/run/memif_wx1,role=client,zero-copy=yes
Attaching a new port...
Port 1 is attached. Now total ports is 2
Done
testpmd> port start 1
Configuring Port 1 (socket 0)
Port 1: 96:75:EE:3F:B7:AA
Checking link statuses...
Done
server:
testpmd> memif_connect(): mmap failed: No such device
testpmd> show port info 1
********************* Infos for port 1 *********************
MAC address: C6:84:F6:36:9F:72
Device name: net_memif1
Driver name: net_memif
Firmware-version: not available
Devargs: socket=/run/memif_wx1,role=server
Connect to socket: 0
memory allocation on the socket: 0
Link status: down
Link speed: 100 Gbps
Link duplex: full-duplex
Autoneg status: On
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-11-10 6:50 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-1825-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.