I don't remember that being a problem. Are you starting them with two different file prefixes and mounting the hugepages directory into both containers?
On Wed, Nov 17, 2021, 22:20 Li Feng <fen...@smartx.com> wrote: > On Thu, Nov 18, 2021 at 2:11 PM Cliff Burdick <shakl...@gmail.com> wrote: > > > > Yes. Try mapping the dpdk metadata directory (/var/run/dpdk) into both > containers from the host. You should be able to do the normal dual process > methods. > > > By the way, if I want to run two separate dpdk processes in two > different dockers, what should I do? > e.g. Running two processes: examples/dpdk-mp_server > These two dockers have mapped the same /dev/hugepages directories. > I have tested, the dpdk will crash because the hugepages are mixed. > > Thanks. > > > > On Wed, Nov 17, 2021, 05:58 Staffan Wiklund <staffan...@gmail.com> > wrote: > >> > >> Hello > >> > >> I wonder if it is possible to use the DPDK multi-process feature in > Docker containers? > >> > >> That is, can a DPDK application execute in a Docker container and share > its > >> DPDK memory with another DPDK application executing in another Docker > container > >> using the DPDK multi-process feature? > >> > >> For example if the DPDK example mp_server executes in one Docker > container: > >> <build_dir>/examples/dpdk-mp_server -l 1-2 -n 4 -- -p 3 -n 2 > >> > >> and the DPDK example mp_client executes in another Docker container: > >> > >> <build_dir>/examples/dpdk-mp_client -l 3 -n 4 --proc-type=auto -- -n 0 > >> > >> Is this possible to implement? > >> > >> Thanks > >> Staffan > >> > >> >
