Lines Matching refs:process

6 Multi-process Support
9 In the DPDK, multi-process support is designed to allow a group of DPDK processes
17 For now, there are two types of process specified:
25 while secondary processes can only run alongside a primary process or
26 after a primary process has already configured the hugepage shared memory for them.
30     Secondary processes should run alongside primary process with same DPDK version.
32     Secondary processes which requires access to physical devices in Primary process, must
35 To support these two process types, and other multi-process setups described later,
38 *   ``--proc-type:`` for specifying a given process instance as the primary or secondary DPDK insta…
43 These are more fully documented in the "Multi- process Sample Application" chapter
49 The key element in getting a multi-process application working using the DPDK is to ensure that
50 memory resources are properly shared among the processes making up the multi-process application.
52 then issues such as inter-process communication (IPC) becomes much simpler.
54 On application start-up in a primary or standalone process,
57 When a secondary process is started, these files are read and the EAL recreates the same memory con…
58 in the secondary process so that all memory zones are shared between processes and all pointers to …
63     Refer to `Multi-process Limitations`_ for details of
66     If the primary process was run with ``--legacy-mem`` or
74    Memory Sharing in the DPDK Multi-process Sample Application
78 whereby a DPDK process is started as a secondary instance if a primary instance is already running.
86 DPDK multi-process support can be used to create a set of peer processes where each process perform…
93 They are described in the "Multi-process Sample Application" chapter in the *DPDK Sample Applicatio…
98 An alternative deployment model that can be used for multi-process applications
99 is to have a single primary process instance that acts as a load-balancer or
104 It is described in the "Multi-process Sample Application" chapter in the *DPDK Sample Application's…
116 Similarly, it creates shared configuration files, memory mapped in each process, using the /var/run…
126 explicitly limited. This is done by passing the ``-m`` flag to each process to
127 specify how much hugepage memory, in megabytes, each process can use (or passing
128 ``--socket-mem`` to specify how much hugepage memory on each socket each process
134     Any network ports being used by one process should be blocked by every other process.
140 this can be trivially extended to multi-process groups of DPDK applications running side-by-side.
142 as the primary process whose shared memory they are connecting to.
149 Multi-process Limitations
152 There are a number of limitations to what can be done when running DPDK multi-process applications.
155 *   The multi-process feature requires that the exact same hugepage memory mappings be present in a…
156     This makes secondary process startup process generally unreliable. Disabling
173     All interrupts are triggered inside the primary process only.
175 …to transfer the interrupt information from the primary process to any secondary process that needs…
178 …since the location of a given function in one process may be different to its location in a second.
179     This prevents the librte_hash library from behaving properly as in a multi-process instance,
182 To work around this issue, it is recommended that multi-process applications perform the hash calcu…
189     which means that only the first, primary DPDK process instance can open and mmap  /dev/hpet.
196 While there are multiple ways one can approach inter-process communication in
206 In other words, any IPC message sent in a primary process will be delivered to
207 all secondaries, while any IPC message sent in a secondary process will only be
208 delivered to primary process. Unicast from primary to secondary or from
252 descriptor either to all secondary processes (if sent from primary process), or
253 to primary process (if sent from secondary process). The function will return