From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 438] memif sock does not honor file-prefix
Date: Sat, 04 Apr 2020 02:42:15 +0000 [thread overview]
Message-ID: <bug-438-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=438
Bug ID: 438
Summary: memif sock does not honor file-prefix
Product: DPDK
Version: 20.02
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
CMD: ./build/l2fwd --vdev=net_tap0 --vdev=net_memif,role=master -l 8,51
--socket-mem=104,0 --socket-limit=1024,0 --file-prefix=custom
--proc-type=primary --no-pci -- -p 0x3 -T 1
Issue: start DPDK application with memif.
observation:
`
EAL: Multi-process socket /var/run/dpdk/custom/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
memif_socket_create(): Failed to setup socket /run/memif.sock: Address already
in use
`
expectation: memif sock interface is to be in `/run/dpdk/custom/memif.sock` and
not `/run/memif.sock`
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-04-04 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 2:42 bugzilla [this message]
2020-04-04 16:54 ` [dpdk-dev] [Bug 438] memif sock does not honor file-prefix Stephen Hemminger
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-438-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.