From: Staffan Wiklund <staffan491@gmail.com>
To: users <users@dpdk.org>
Subject: How to use DPDK memif between Docker container and native Linux application?
Date: Wed, 16 Feb 2022 10:19:02 +0100 [thread overview]
Message-ID: <CAAV4wTjT03dBJmVPLKWrPjrnv3pETUzfpH13GaS8z8SUtAdoVw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
Hello
I wonder if it is possible for a DPDK application using the memif feature
to communicate with a native Linux application?
I have tried to create a Docker container and start the image by:
docker run -ti --privileged -v "/mnt/huge:/mnt/huge" -v "/var/run:/var/run"
-v "/tmp:/tmp" -v "/run:/run" -v "/sys:/sys" -v "/dev:/dev" testpmd
/bin/bash
In this container I start the dpdk-testpmd application in server mode by:
./dpdk-testpmd -l 1-2 --no-pci --proc-type=primary --file-prefix=td1
--vdev=net_memif,role=server,mac=00:00:00:00:00:01 -- -i
From a UNIX shell in the same server I start the dpdk-testpmd in client
mode:
sudo ./dpdk-testpmd -l 3-4 --no-pci --proc-type=primary --file-prefix=td2
--vdev=net_memif,zero-copy=yes,mac=00:00:00:00:00:02 --single-file-segments
-- -i
This results in the following error message on the client side:
. . .
Configuring Port 0 (socket 0)
memif_connect_client(): Failed to connect socket: /run/memif.sock.
Fail to start port 0
. . .
If I start both sides in a UNIX shell, the client can connect to the server.
Do you know what can be the fault when executing in a Docker container and
in a UNIX shell for communication using the DPDK memif feature?
Thanks
Staffan
[-- Attachment #2: Type: text/html, Size: 1632 bytes --]
next reply other threads:[~2022-02-16 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:19 Staffan Wiklund [this message]
2022-02-16 18:46 ` Stephen Hemminger
2022-02-16 19:09 ` Staffan Wiklund
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=CAAV4wTjT03dBJmVPLKWrPjrnv3pETUzfpH13GaS8z8SUtAdoVw@mail.gmail.com \
--to=staffan491@gmail.com \
--cc=users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).