On Sat, 04 Apr 2020 02:42:15 +0000 bugzi...@dpdk.org wrote: > 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.vargh...@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`
If it just used abstract socket type it would not have this problem.
