DPDK多进程模式

多进程模式

1、Symmetric/Peer Processes

主从进程执行同样的任务，分摊保卫转发

2、Asymmetric/Non-Peer Processes

客户端进程+服务端进程，服务进程收包并分发给不同的从进程（客户端进程）

3、Running Multiple Independent DPDK Applications

多主进程方式，多个主进程独立运行，使用–file-prefix区分文件目录

4、Running Multiple Independent Groups of DPDK Applications

多进程组，多个主进程，每个主进程又有个多个从进程。不同组独立运行。同一个组共享资源（内存、网卡等）

多进程限制

Depending upon the hardware in use, and the number of DPDK processes used, it may not be possible to have HPET timers available in each DPDK instance. The minimum number of HPET comparators available to Linux* userspace can be just a single comparator, which means that only the first, primary DPDK process instance can open and mmap /dev/hpet. If the number of required DPDK processes exceeds that of the number of available HPET comparators, the TSC (which is the default timer in this release) must be used as a time source across all processes instead of the HPET.

Since the memory subsystem uses IPC internally, memory allocations and IPC must not be mixed: it is not safe to use IPC inside a memory-related callback, nor is it safe to allocate/free memory inside IPC callbacks. Attempting to do so may lead to a deadlock.